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 Joaquin.Cuenca.Abela
Recipients Joaquin.Cuenca.Abela, athomas, esam, r.david.murray
Date 2010-03-03.11:22:56
SpamBayes Score 0.0038927419
Marked as misclassified No
Message-id <>

RFC 2046, 5.1.1 refers to the CRLF that happens just before the boundary. It says nothing about an encoded CRLF.

From Andreas example, if you have:

Content-Type: text/plain; name="test.txt"
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="test.txt"


You are correctly eating the CRLF that exists between MTIzCg== and --------------040103020004000509010404--, because it's part of the boundary.

You are also eating the CRLF that is inside the base64 encoded text, and I agree with Andreas that this is incorrect. Will you please consider reopening this bug?
Date User Action Args
2010-03-03 11:22:58Joaquin.Cuenca.Abelasetrecipients: + Joaquin.Cuenca.Abela, r.david.murray, athomas, esam
2010-03-03 11:22:58Joaquin.Cuenca.Abelasetmessageid: <>
2010-03-03 11:22:56Joaquin.Cuenca.Abelalinkissue7143 messages
2010-03-03 11:22:56Joaquin.Cuenca.Abelacreate