Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix several issues in CONNECT Control Packet marshaller (changes API) #112

Merged
merged 2 commits into from
Aug 21, 2017

Conversation

KonstantinRitt
Copy link
Contributor

No description provided.

Per to MQTT 3.1.1 Standard:
> If the User Name Flag is set to 0, the Password Flag MUST be set to 0 [MQTT-3.1.2-22].
Per to MQTT 3.1.1 Standard:

> 3.1.3.3 Will Message
> If the Will Flag is set to 1 the Will Message is the next field in the payload. The Will Message defines the Application Message that is to be published to the Will Topic as described in Section 3.1.2.5. This field consists of a two byte length followed by the payload for the Will Message expressed as a sequence of zero or more bytes. The length gives the number of bytes in the data that follows and does not include the 2 bytes taken up by the length itself.

> 3.1.3.5 Password
> If the Password Flag is set to 1, this is the next field in the payload. The Password field contains 0 to 65535 bytes of binary data prefixed with a two byte length field which indicates the number of bytes used by the binary data (it does not include the two bytes taken up by the length field itself).
@KonstantinRitt KonstantinRitt changed the title Connect 311 Fix several issues in CONNECT Control Packet marshaller (changes API) Aug 17, 2017
@mwallnoefer mwallnoefer merged commit 915c2ad into emqx:master Aug 21, 2017
@KonstantinRitt KonstantinRitt deleted the connect_311 branch August 21, 2017 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants