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
yes, our customers have mqtt servers with usernames and passwords containing spaces, @ and other special characters.
Telling them to correctly urlencode the parameters didnt help.
We only expose one single mqtt connection url and not the individual username and password fields.
Describe the solution you'd like.
The mqtt library should urldecode automatically if the username and passwords are taken from the url
Describe alternatives you've considered.
No response
Additional context.
No response
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
mqtt does not url decode username or password
mqtt does not url decode username or password (IDFGH-14444)
Jan 16, 2025
github-actionsbot
changed the title
mqtt does not url decode username or password (IDFGH-14444)
mqtt does not url decode username or password (IDFGH-14444) (IDFGH-14446)
Jan 16, 2025
Could you add more details on use case, failures that are preventing, if possible some test cases and the broker version so if we decide to implement the feature we can test it?
Is your feature request related to a problem?
yes, our customers have mqtt servers with usernames and passwords containing spaces, @ and other special characters.
Telling them to correctly urlencode the parameters didnt help.
We only expose one single mqtt connection url and not the individual username and password fields.
Describe the solution you'd like.
The mqtt library should urldecode automatically if the username and passwords are taken from the url
Describe alternatives you've considered.
No response
Additional context.
No response
The text was updated successfully, but these errors were encountered: