This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients barry, mkaiser, r.david.murray
Date 2019-12-13.17:38:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks for the report.  Can you provide an example that reproduces the problem?  

Per the RFC, lines may be broken before whitespace in certain places in certain headers, but that does not make the whitespace go away.  Only the crlf sequence is removed when unfolding the header, per the RFC, so your proposed fix is incorrect. I suspect your example header is invalid, and the question will then become is there some sort of Postel-style error recovery we can and want to do in the function that parses the content-disposition header.
Date User Action Args
2019-12-13 17:38:36r.david.murraysetrecipients: + r.david.murray, barry, mkaiser
2019-12-13 17:38:36r.david.murraysetmessageid: <>
2019-12-13 17:38:36r.david.murraylinkissue39040 messages
2019-12-13 17:38:36r.david.murraycreate