peter-pe

# 21.Violation 21 According to the specification of MQTTv3.1.1: The payload of a SUBSCRIBE packet MUST contain at least one Topic Filter / QoS pair. The parse_subscribe_packet function in the...

# 22.Violation 22 According to the specification of MQTTv3.1.1: Additionally, Topic Names and Topic Filters must be UTF-8 encoded strings that do not exceed 65535 bytes in length. The code...

# 23.Violation 23 According to the specification of MQTTv3.1.1: When the Server receives a SUBSCRIBE Packet from a Client, the Server MUST respond with a SUBACK Packet [MQTT-3.8.4-1]. The function...

# 24.Violation 24 According to the specification of MQTTv3.1.1: The multi-level wildcard character MUST be the last character specified in the Topic Filter when it is specified either on its...

# 25.Violation 25 According to the specification of MQTTv3.1.1: If a subscribing Client has been granted maximum QoS 1 for a particular Topic Filter, a QoS 2 Message published to...

# 26.Violation 26 According to the specification of MQTTv3.1.1: The Topic Filters in an UNSUBSCRIBE packet MUST be UTF-8 encoded strings as defined in Section 1.5.3, packed contiguously [MQTT-3.10.3-1]. The...

# 27.Violation 27 According to the specification of MQTTv3.1.1: The Server MUST respond to an UNSUBSCRIBE request by sending an UNSUBACK packet. The code violates the MQTT 3.1.1 rule that...

# 28.Violation 28 According to the specification of MQTTv3.1.1: If a server receives a valid CONNECT packet but cannot process the request, the server must send a CONNACK packet with...

# 29.Violation 29 According to the specification of MQTTv3.1.1: If the Server rejects the CONNECT Packet, the Server MUST NOT process any data sent by the Client after the CONNECT...