-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi,
> Your argument is that the BTS should send a text/plain MIME document > with LF instead of CRLF, which conflicts with RFC 2046. > > Frankly, I think that's probably more sane, but that's because I think > that the MIME standard is wrong is specifying a line ending standard > for documents which have been QP or base64 encoded, and pine is wrong > in changing the line encoding. I fully agree with your opinion about the brokeness of MIME. Concerning HTTP, I'm sorry to contradict you, but from RFC 2616, Appendix 19.4.1: HTTP is not a MIME-compliant protocol. [...] And 19.4.2: [...] Where it is possible, a proxy or gateway from HTTP to a strict MIME environment SHOULD translate all line breaks within the text media types described in section 3.7.1 of this document to the RFC 2049 canonical form of CRLF. [...] This implies that HTTP-documents are *not* canonicalized, if the RFC authors found it necessary to give advice on how to convert HTTP datasets to MIME-compliant data. Cheers, Nik - -- * mirabilos is handling my post-1990 smartphone * <mirabilos> Aaah, it vibrates! Wherefor art thou, daemonic device?? PGP fingerprint: 2086 9A4B E67D 1DCD FFF6 F6C1 59FC 8E1D 6F2A 8001 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQFOBAEBCAA4BQJQyN3vMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQWfyOHW8qgAH2+ggAkrq1y7BdbSm7mHsVOLBt liqVIR3N12vH92y4oA4kCdboX+S5SYJelonFJPGqcL0myrQhZeuhLiSIsVDgv1uh d1NbTq5zVy7Wom70TmECAxL4pewBQIJ66Xg0f8j34JN62O3OGDZxRBKmYZCginYQ X61fn9KcdtxE4KnV3bpJKddWhYmQiuSwZupYxmVh0Z3yQUytW2U00hAlQ24xEoyW jH/Xq7SIGiuSlOpvqHptxVUn+tI75NWa4Xns2xd7LjhJbeg4j3MkBqfYmeWGSRX4 XZ3v7Bifx+wkHJEbQkYv+eCRyGm+PvUV6RX5OYn8X4Pn6gXYWKDib0UeT6VWd1pX gw== =lnYy -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
