[3.7] bpo-42967: only use '&' as a query string separator (GH-24297) #24531
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
bpo-42967: [security] Address a web cache-poisoning issue reported in urllib.parse.parse_qsl(). urllib.parse will only us "&" as query string separator by default instead of both ";" and "&" as allowed in earlier versions. An optional argument seperator with default value "&" is added to specify the separator. Co-authored-by: Éric Araujo <[email protected]> Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com> Co-authored-by: Ken Jin <[email protected]> Co-authored-by: Éric Araujo <[email protected]> (cherry picked from commit fcbe0cb)
bpo-42967: [security] Address a web cache-poisoning issue reported in urllib.parse.parse_qsl(). urllib.parse will only us "&" as query string separator by default instead of both ";" and "&" as allowed in earlier versions. An optional argument seperator with default value "&" is added to specify the separator. Co-authored-by: Éric Araujo <[email protected]> Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com> Co-authored-by: Ken Jin <[email protected]> Co-authored-by: Éric Araujo <[email protected]>. (cherry picked from commit fcbe0cb) Co-authored-by: Adam Goldschmidt <[email protected]>
orsenthil
commented
Feb 15, 2021
Doc/library/urllib.parse.rst
Outdated
| .. versionchanged:: 3.7.2 | ||
| Added *max_num_fields* parameter. | ||
|
|
||
| .. versionchanged:: 3.10 |
Contributor
|
@orsenthil Should I be the one to change the versions in all PRs? Asking cause I'm not familiar with the process. |
Member
Author
|
@AdamGold - Nope. My comments were for me as placeholders, I made it so that I can I get back to these. Having said that, once ready, I will ping you to review these backports to see if everything is alright and we could merge them. |
Member
Author
|
Hi Ned, the patch against 3.7 is complete. You could merge this when you get a chance and cut the release. Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
[3.7] bpo-42967: only use '&' as a query string separator (GH-24297)
Backport of fcbe0cb to 3.7
https://bugs.python.org/issue42967
https://bugs.python.org/issue42967