🐛 fix unquote issue with querystring handling. #1264
Merged
Conversation
This file contains 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
|
this should be fixed... |
hellno
approved these changes
Sep 6, 2023
…-supported' into fix/ampersand-in-querystring-not-supported
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.
Description
Reverts unquote usage when preparing the wsgi environ "QUERY_STRING".
A previous request (#879) was raised to have the content of the "QUERY_STRING" value unquoted (percent encoding decoded), however, it was later reported that the introduction of
unquotecaused an issue in querystring parsing in flask. (#1227)This PR updates and adds testcases to assure that the "queryStringParameters" are properly converted into the "QUERY_STRING" value required by wsgi environ.
GitHub Issues
#1227