bpo-42967: Don't treat semicolon as a separator in urllib.parse #24271
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
| Also waiting on some consensus on whether this is a security issue or not in the bpo before I add blurb. |
| I closed this PR in favor of #24297 because I think it would be better to have a single PR to not split core devs' attention. Apologies to all for any inconvenience caused. |
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.
I wonder if this should be the default behaviour?
I'll update docs once we decide on that ^,
TODO: Update Public API of FieldStorage, FieldStorage.read_multi, parse and parse_multipart.Co-Authored-By: Adam Goldschmidt adamgold7@gmail.com
https://bugs.python.org/issue42967