-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
mount_point not removed on outgoing messages (version 2) #2244
Labels
Component: mosquitto-broker
Status: Completed
Nothing further to be done with this issue, it can be closed by the requestor or committer.
Type: Bug
Milestone
Comments
Can confirm, I see this same problem on my MQTT server. |
Yep, i can also confirm this in v2.0.11. |
Same problem here (also 2.0.11). |
Thank you, that is now fixed and will be part of 2.0.12 shortly. I've also improved the mount point test to cover this situation. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Component: mosquitto-broker
Status: Completed
Nothing further to be done with this issue, it can be closed by the requestor or committer.
Type: Bug
Version: current 2.0.11 from docker
mosquitto.conf:
per_listener_settings true
listener 1883
protocol mqtt
allow_anonymous true
listener 1884
protocol mqtt
mount_point foo/
allow_anonymous true
Client A:
mosquitto_sub -t '#' -p 1883 -v
Client B:
mosquitto_sub -t '#' -p 1884 -v
With mosquitto 2.0.11:
When sending with
mosquitto_pub -t 'bas' -m 'hi' -p 1884
:Client A: foo/bas hi -- As expected. The mount_point foo/ is prepended to 'bas', and it arrives as coming from 'foo/bas'.
Client B: foo/bas hi -- Not as expected. The mount_point foo/ should have been removed.
With mosquitto 1.6:
When sending with
mosquitto_pub -t 'bas' -m 'hi' -p 1884
:Client A: foo/bas hi -- As expected. The mount_point foo/ is prepended to 'bas', and it arrives as coming from 'foo/bas'.
Client B: bas hi -- As expected. the mount_poiint foo/ is removed, and it arrives as coming from 'bas'
The text was updated successfully, but these errors were encountered: