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

make Mosquitto happy #2494

Merged
merged 1 commit into from
Nov 27, 2023
Merged

make Mosquitto happy #2494

merged 1 commit into from
Nov 27, 2023

Conversation

scaprile
Copy link
Collaborator

If the MQTT over WS broker is not port based, that is, it does not assume that the protocol carried by the WebSocket connection will be MQTT based on the port number, then, if we can't change it, we need to add an extra header in the connection request, in order to negotiate that: Sec-Websocket-Protocol: mqtt

Many clients default to doing that, so maybe we should also default to that in our example

@scaprile scaprile requested a review from cpq November 26, 2023 18:42
@cpq cpq merged commit 8022635 into master Nov 27, 2023
126 checks passed
@cpq cpq deleted the mqttws branch November 27, 2023 13:13
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