summaryrefslogtreecommitdiffstats
path: root/Python
diff options
context:
space:
mode:
authorƁukasz Langa <lukasz@langa.pl>2024-09-04 15:36:17 (GMT)
committerGitHub <noreply@github.com>2024-09-04 15:36:17 (GMT)
commitb158a76ce094897c870fb6b3de62887b7ccc33f1 (patch)
treeae4fde7fd5bcf6b7b170030ba69308f489774d3d /Python
parente319f774f9e766a2b92949444a2d46081df3363a (diff)
downloadcpython-b158a76ce094897c870fb6b3de62887b7ccc33f1.zip
cpython-b158a76ce094897c870fb6b3de62887b7ccc33f1.tar.gz
cpython-b158a76ce094897c870fb6b3de62887b7ccc33f1.tar.bz2
[3.8] gh-121650: Encode newlines in headers, and verify headers are sound (GH-122233) (#122611)
Per RFC 2047: > [...] these encoding schemes allow the > encoding of arbitrary octet values, mail readers that implement this > decoding should also ensure that display of the decoded data on the > recipient's terminal will not cause unwanted side-effects It seems that the "quoted-word" scheme is a valid way to include a newline character in a header value, just like we already allow undecodable bytes or control characters. They do need to be properly quoted when serialized to text, though. This should fail for custom fold() implementations that aren't careful about newlines. (cherry picked from commit 097633981879b3c9de9a1dd120d3aa585ecc2384) Co-authored-by: Petr Viktorin <encukou@gmail.com> Co-authored-by: Bas Bloemsaat <bas@bloemsaat.org> Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
Diffstat (limited to 'Python')
0 files changed, 0 insertions, 0 deletions