BUGFIX: Fix RedisBackend
to allow scheme in hostname
#3146
Merged
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.
The hostname can hold a scheme, that is needed to enable TLS for the connection:
or
This change fixes the overly naive check for a unix socket to allow using a scheme in the hostname together with a custom port.
Review instructions
Have an TLS enabled Redis (e.g. free tier on upstash.com) and try to connect to it…
Checklist
FEATURE|TASK|BUGFIX
Reviewer - Breaking Changes are marked wit!!!
and have upgrade-instructions