Christopher Faulet 0de0becf0b BUG/MINOR: mqtt: Support empty client ID in CONNECT message ... As specified by the MQTT specification (MQTT-3.1.3-6), the client ID may be empty. That means the length of the client ID string may be 0. However, The MQTT parser does not support empty strings. So, to fix the bug, the mqtt_read_string() function may now parse empty string. 2 bytes must be found to decode the string length, but the length may be 0 now. It is the caller responsibility to test the string emptiness if necessary. In addition, in mqtt_parse_connect(), the client ID may be empty now. This patch should partely fix the issue #1310. It must be backported to 2.4.		2021-06-28 16:29:44 +02:00
..
digest.vtc
field.vtc
fix.vtc
hmac.vtc
iif.vtc
json_query.vtc	REGTESTS: disable inter-thread idle connection sharing on sensitive tests	2021-05-09 14:41:41 +02:00
json.vtc	REGTESTS: Remove REQUIRE_VERSION=1.6 from all tests	2021-06-11 19:21:28 +02:00
mqtt.vtc	BUG/MINOR: mqtt: Support empty client ID in CONNECT message	2021-06-28 16:29:44 +02:00
secure_memcmp.vtc	REGTESTS: disable inter-thread idle connection sharing on sensitive tests	2021-05-09 14:41:41 +02:00
sha2.vtc
url_dec.vtc	REGTESTS: Remove REQUIRE_VERSION=1.6 from all tests	2021-06-11 19:21:28 +02:00
url_enc.vtc