You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has a big implication, as it causes errors on subscriptions (cannot subscribe as topic cannot be decoded) and also on publish events receives payloads with extra 00 byte at the begining, corresponding to undecoded properties:
Server is sending the content with the space for properties but client is not consuming them, so there are some bytes not being consumed and being left in payload.
Also on the contrary, the client sends a packet with properties bytes codified, and then server is not consuming the properties so they remain in payload, making payload to be displaced so cannot be correctly decoded:
After digging a little bit on the library, found what it seems a bug, or at least a miss-documentation. It has mainly affectations on 5.0.
Outputs
undefined
.Outputs
{ protocolVersion: 5, protocolId: 'MQTT' }
.Outputs:
Outputs:
This has a big implication, as it causes errors on subscriptions (cannot subscribe as topic cannot be decoded) and also on publish events receives payloads with extra 00 byte at the begining, corresponding to undecoded properties:
Server is sending the content with the space for properties but client is not consuming them, so there are some bytes not being consumed and being left in payload.
Also on the contrary, the client sends a packet with properties bytes codified, and then server is not consuming the properties so they remain in payload, making payload to be displaced so cannot be correctly decoded:
from parser.js:
The other point is that options are being overridden by
connectPacket
in connection.jsThe text was updated successfully, but these errors were encountered: