Message100338
Hi,
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"
MTIzCg==
--------------040103020004000509010404--
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:58 | Joaquin.Cuenca.Abela | set | recipients:
+ Joaquin.Cuenca.Abela, r.david.murray, athomas, esam |
2010-03-03 11:22:58 | Joaquin.Cuenca.Abela | set | messageid: <1267615378.39.0.902858703138.issue7143@psf.upfronthosting.co.za> |
2010-03-03 11:22:56 | Joaquin.Cuenca.Abela | link | issue7143 messages |
2010-03-03 11:22:56 | Joaquin.Cuenca.Abela | create | |
|