summaryrefslogtreecommitdiffstats
path: root/Misc
diff options
context:
space:
mode:
authorAbhilash Raj <maxking@users.noreply.github.com>2020-05-29 00:04:59 (GMT)
committerGitHub <noreply@github.com>2020-05-29 00:04:59 (GMT)
commit21017ed904f734be9f195ae1274eb81426a9e776 (patch)
tree407b8d0170e82598d769d6b8dcb439323cb9b930 /Misc
parentc610d970f5373b143bf5f5900d4645e6a90fb460 (diff)
downloadcpython-21017ed904f734be9f195ae1274eb81426a9e776.zip
cpython-21017ed904f734be9f195ae1274eb81426a9e776.tar.gz
cpython-21017ed904f734be9f195ae1274eb81426a9e776.tar.bz2
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.
Diffstat (limited to 'Misc')
-rw-r--r--Misc/NEWS.d/next/Library/2019-12-15-18-47-20.bpo-39040.tKa0Qs.rst2
1 files changed, 2 insertions, 0 deletions
diff --git a/Misc/NEWS.d/next/Library/2019-12-15-18-47-20.bpo-39040.tKa0Qs.rst b/Misc/NEWS.d/next/Library/2019-12-15-18-47-20.bpo-39040.tKa0Qs.rst
new file mode 100644
index 0000000..078bce2
--- /dev/null
+++ b/Misc/NEWS.d/next/Library/2019-12-15-18-47-20.bpo-39040.tKa0Qs.rst
@@ -0,0 +1,2 @@
+Fix parsing of invalid mime headers parameters by collapsing whitespace between
+encoded words in a bare-quote-string.