Repository navigation
Preserve spaces in connection URL passwords - #670
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Passwords containing spaces fail authentication when PGSync builds database, search, or Redis connection URLs. For example,
demo password+with@symbolsis encoded withquote_plusand decoded by URL consumers asdemo+password+with@symbols.Use URL percent-encoding (
quote(..., safe="")) for passwords in the URL userinfo component, so spaces become%20and literal plus signs remain%2B. Keep existing auth-plugin precedence and explicit-URL overrides.Validation:
tests/test_urls.pypass after the fix.isort --profile black --check-only,black --check,flake8, andgit diff --checkpass for the changed Python files.The tests do not require external services. The full database/backend matrix is left to upstream CI.