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 Lukasa
Recipients Lukasa, barry, icordasc, mgdelmonte, r.david.murray
Date 2015-06-02.22:11:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1433283113.99.0.0650830202907.issue24363@psf.upfronthosting.co.za>
In-reply-to
Content
This is one of those bugs that's actually super tricky to correctly fix.

The correct path is to have the goal of conservatively accepting as many headers as possible. Probably this means looking ahead to the next few lines and seeing if they appear to roughly keep a header structure (\r\n line breaks and colon separated values). However, I'm not entirely sure how to structure that sentiment in code at this time.
History
Date User Action Args
2015-06-02 22:11:54Lukasasetrecipients: + Lukasa, barry, r.david.murray, icordasc, mgdelmonte
2015-06-02 22:11:53Lukasasetmessageid: <1433283113.99.0.0650830202907.issue24363@psf.upfronthosting.co.za>
2015-06-02 22:11:53Lukasalinkissue24363 messages
2015-06-02 22:11:53Lukasacreate