fix: decode + as space in options startup parameter#976
Merged
Conversation
URL form-encoding uses + for spaces, but libpq only decodes %xx percent-encoding (RFC 3986), leaving + literal in the startup message. This caused pgdog.role and other options to be silently ignored when the connection URL used + instead of %20.
|
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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
3 participants
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.
URL form-encoding uses + for spaces, but libpq only decodes %xx percent-encoding (RFC 3986), leaving + literal in the startup message. This caused pgdog.role and other options to be silently ignored when the connection URL used + instead of %20.
We hit this problem while configuring airflow connections (Google Cloud Composer managed) through their extra (JSON) field.