Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.7] bpo-43882 - Mention urllib.parse changes in Whats New section for 3.7.11 #26267

Merged
merged 2 commits into from
May 20, 2021
+10 −0
Merged

[3.7] bpo-43882 - Mention urllib.parse changes in Whats New section for 3.7.11 #26267

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3afcf18
Add What's New for bpo-43882 - urllib.parse should sanitize urls cont…
orsenthil May 20, 2021
5aec800
add "a new"
gpshead May 20, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions Doc/whatsnew/3.7.rst
View file
Original file line number Diff line number Diff line change
@@ -2594,3 +2594,13 @@ IPv4 address sent from the remote server when setting up a passive data
channel. We reuse the ftp server IP address instead. For unusual code
requiring the old behavior, set a ``trust_server_pasv_ipv4_address``
attribute on your FTP instance to ``True``. (See :issue:`43285`)


The presence of newline or tab characters in parts of a URL allows for some
forms of attacks. Following the WHATWG specification that updates RFC 3986,
ASCII newline ``\n``, ``\r`` and tab ``\t`` characters are stripped from the
URL by the parser :func:`urllib.parse` preventing such attacks. The removal
characters are controlled by a new module level variable
``urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE``. (See :issue:`43882`)