[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (MQTT-9) If the Connect flags indicate that he user name exists but none is present in the payload treat this as a malformed CONNECT packet.
[ http://tools.oasis-open.org/issues/browse/MQTT-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33543#action_33543 ] Rahul Gupta commented on MQTT-9: -------------------------------- This is the current documentation in the working draft, which was copied from the 3.1 specification: "If the password flag is set but the password is not present the server MUST disconnect the TCP socket" which eventually is because of a malformed CONNECTpacket. I think the client should be informed with a error code from Server, through CONNACK before doing a abrupt DISCONNECT > If the Connect flags indicate that he user name exists but none is present in the payload treat this as a malformed CONNECT packet. > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: MQTT-9 > URL: http://tools.oasis-open.org/issues/browse/MQTT-9 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Improvement > Components: core > Environment: MQTT Server > Reporter: Andrew Banks > > If the Connect flags indicate that the user name exists but none is present in the payload treat this as a malformed CONNECT packet and disconnect the client. > See issue-8 as to whether a connack is flowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]