Sentinels: Fix password with special characters for master #66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When having some sentinels and a master behind them, and the master is protected by a password including some special characters, the client is not able to connect to master, the error is:
bad password component
I investigated and this happens because the sentinels client calls
Enpoint#for
:async-redis/lib/async/redis/sentinel_client.rb
Line 111 in edc87b7
which ends up sending the credentials to a new
URI::Generic
instance:async-redis/lib/async/redis/endpoint.rb
Line 85 in edc87b7
This results in the above password error unless the password is properly URL encoded, however, in my local tests, Redis will reject the password as incorrect when receiving it encoded. To solve this I think the best solution is to not send the credentials to the URI instance at all, instead, send the credentials directly to the
Endpoint
initializer, that way there's no need to encode the password and Redis accepts it.This works for me. Here is the script I use to make my tests locally:
Types of Changes
Contribution