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 mgdelmonte
Recipients Lukasa, barry, demian.brecht, icordasc, mgdelmonte, r.david.murray
Date 2015-06-03.00:16:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I don't want to speak out of school and you guys certainly know what you're doing, but it seems a shame to go through these gyrations -- lookahead plus "unreading" lines -- only to preserve the ability to parse email headers, when HTTP really does follow a different spec.  My suggestion would be to examine the header and decide, if it's HTTP, to just ignore nonconforming lines; and if it's email, then the problem is already solved (as email doesn't have encoding rules that would cause problems later).  

My fear would be that you'll eventually get that nonconforming line with leading whitespace, which will lead right back to the same error.
Date User Action Args
2015-06-03 00:16:28mgdelmontesetrecipients: + mgdelmonte, barry, r.david.murray, icordasc, demian.brecht, Lukasa
2015-06-03 00:16:28mgdelmontesetmessageid: <>
2015-06-03 00:16:27mgdelmontelinkissue24363 messages
2015-06-03 00:16:26mgdelmontecreate