[issue26686] email.parser stops parsing headers too soon when given a defective message.

Martin Panter added the comment: Thanks David. Since I am more intersted in fixing this robustly for HTTP and similar protocols, I might focus on just Issue 24363. Either confine my changes to the existing HTTP (or new) policy and start using that, or just address this from the HTTP package.

[issue26686] email.parser stops parsing headers too soon when given a defective message.

R. David Murray added the comment: I would prefer if we did lookahead to see if the subsequent line looks like a header. It's more complicated to do that, of course, and could still lead to false negatives. However, I think that would probably retain enough backward compatibility to be

[issue26686] email.parser stops parsing headers too soon when given a defective message.

Martin Panter added the comment: . It would be nice to get feedback if my patch is sensible, especially from people familiar with normal usage of the “email” module, as opposed with the usage by the HTTP module. -- stage: -> patch review ___

[issue26686] email.parser stops parsing headers too soon when given a defective message.

Changes by ppperry : -- title: email.parser stops parsing headers too soon. -> email.parser stops parsing headers too soon when given a defective message. ___ Python tracker

[issue26686] email.parser stops parsing headers too soon.

Martin Panter added the comment: FWIW in the HTTP bug , David said “when seeing a line that doesn't look like a header the error recovery is to treat that line as the beginning of the body (ie: assume the blank line is missing).” I have no

[issue26686] email.parser stops parsing headers too soon.

Martin Panter added the comment: Also see Issue 24363, basically the same bug in the HTTP parser, which (ab?)uses the email package to do most of the work. In that case, according to my note the faulty header field ends with: X-Frame-Options: SAMEORIGIN\r\n Set-Cookie: mb-CookieP=; HttpOnly;

[issue26686] email.parser stops parsing headers too soon.

Changes by SilentGhost : -- components: +email nosy: +barry, r.david.murray versions: +Python 3.5 -Python 3.4 ___ Python tracker

[issue26686] email.parser stops parsing headers too soon.

Mark Sapiro added the comment: Added Python 2.7 to versions: -- versions: +Python 2.7 ___ Python tracker ___

[issue26686] email.parser stops parsing headers too soon.

New submission from Mark Sapiro: Given an admittedly defective (the folded Content-Type: isn't indented) message part with the following headers/body --- Content-Disposition: inline; filename="04EBD_._A546BB.zip" Content-Type: application/x-rar-compressed;