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
{{ message }}
This repository has been archived by the owner on Feb 11, 2020. It is now read-only.
If a client is subscribing a qos=1 topic, but not issuing the subscribe command on each reconnect, retained messages are not forwarded, however I think they should!
This is since forwardRetained is called inside handleSubscribe https://github.com/mcollina/mosca/blob/master/lib/client.js#L496, but should be moved inside restoreClientSubscriptions or authorizeSubscribe so that it gets called on each subscription restore.
The text was updated successfully, but these errors were encountered:
I do not think retained messages should be forwarded in this case.
Have you tried this with mosquitto or another MQTT broker and checked if they behave like Mosca?
client A has a QoS 1 subscription
client A goes offline
client B publishes a retained message with QoS 0
client A should or should not receive the retained message
I think it should not. If this is still unclear from the spec, we might ask it to be clarified/fixed.
If a client is subscribing a qos=1 topic, but not issuing the subscribe command on each reconnect, retained messages are not forwarded, however I think they should!
This is since
forwardRetained
is called inside handleSubscribe https://github.com/mcollina/mosca/blob/master/lib/client.js#L496, but should be moved inside restoreClientSubscriptions or authorizeSubscribe so that it gets called on each subscription restore.The text was updated successfully, but these errors were encountered: