]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
bpo-39040: Fix parsing of email mime headers with whitespace between encoded-words...
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Fri, 29 May 2020 11:43:27 +0000 (04:43 -0700)
committerGitHub <noreply@github.com>
Fri, 29 May 2020 11:43:27 +0000 (04:43 -0700)
commit6381ee077d3c69d2f947f7bf87d8ec76e0caf189
treedaa4c61c903d3a39d7ee1b4eb0d118c614f9e7b6
parentf89d7bcdeed22382aa2af5e3b3e1c68d21004bcb
bpo-39040: Fix parsing of email mime headers with whitespace between encoded-words. (gh-17620)

* bpo-39040: Fix parsing of email headers with encoded-words inside a quoted string.

It is fairly common to find malformed mime headers (especially content-disposition
headers) where the parameter values, instead of being encoded to RFC
standards, are "encoded" by doing RFC 2047 "encoded word" encoding, and
then enclosing the whole thing in quotes.  The processing of these malformed
headers was incorrectly leaving the spaces between encoded words in the decoded
text (whitespace between adjacent encoded words is supposed to be stripped on
decoding).  This changeset fixes the encoded word processing inside quoted strings
(bare-quoted-string) to do correct RFC 2047 decoding by stripping that
whitespace.
(cherry picked from commit 21017ed904f734be9f195ae1274eb81426a9e776)

Co-authored-by: Abhilash Raj <maxking@users.noreply.github.com>
Lib/email/_header_value_parser.py
Lib/test/test_email/test_headerregistry.py
Misc/NEWS.d/next/Library/2019-12-15-18-47-20.bpo-39040.tKa0Qs.rst [new file with mode: 0644]