peter-pe

# 11.Violation 11 According to the specification of MQTTv3.1.1: If the Server performs checks on the CONNECT Packet contents for further restrictions or authentication and authorization and any of these...

# 12.Violation 12 According to the specification of MQTTv3.1.1: The Topic Name in the PUBLISH Packet MUST NOT contain wildcard characters [MQTT-3.3.2-2]. The code violates MQTT-3.3.2-2 by processing PUBLISH packets...

# 13.Violation 13 According to the specification of MQTTv3.1.1: When a published message matches multiple subscription filters due to overlapping Client subscriptions with wildcards, the Server MUST deliver the message...

# 14.Violation 14 According to the specification of MQTTv3.1.1: If a Server implementation rejects a Client's PUBLISH request, the Server MUST either acknowledge the PUBLISH request according to standard QoS...

# 15.Violation 15 According to the specification of MQTTv3.1.1: The wildcard characters can be used in Topic Filters, but these characters MUST NOT be used within a Topic Name to...

# 16.Violation 16 According to the specification of MQTTv3.1.1: When a Server takes ownership of an incoming Application Message, the Server MUST add the message to the Session state of...

# 17.Violation 17 According to the specification of MQTTv3.1.1: If the RETAIN flag is set to 1 in a PUBLISH Packet sent by a Client to a Server, the Server...

# 18.Violation 18 According to the specification of MQTTv3.1.1: In the QoS 2 delivery protocol, the Receiver MUST respond with a PUBREC containing the Packet Identifier from the incoming PUBLISH...

# 19.Violation 19 According to the specification of MQTTv3.1.1: The Server SHOULD prevent Clients from using Topic Names starting with a wildcard character to exchange messages with other Clients. There...

# 20.Violation 20 According to the specification of MQTTv3.1.1: The Topic Filters in a SUBSCRIBE packet payload MUST be UTF-8 encoded strings as defined in Section 1.5.3 [MQTT-3.8.3-1]. The code...