Stefano Bagnara wrote:
I've had a fast read of the RFC2822 about this issue. It insists that
CRLF is the only valid delimiter for a canonical rfc822 message.
Furthermore rfc2822 does not allow the use of isolated CR or LF.
So, whenever isolated CR or isolated LF is found we have a malformed
rfc822 message and we have to define how to deal with it.
Tell the users of IE about it
I don't understand why a conversion is wrong for the http case (when
does it happen that you have to deal with isolated LF ?).
How about binary data in multipart/form encoded requests?
So we have options:
1) fail parsing anything containing isolated CR or LF chars.
2) parse isolated CR or isolated LF as CRLF and in this case:
a. make sure we output well formed rfc2822 message (CRLF only)
b. keep bad newlines as is (more difficult to implement)
c. randomly convert only some of them (as we do now)
With regard to #2 we also have to decide whether the choice also applies
to parsing of Base64 encoded nested rfc822 messages or not.
Stefano
Whatever you opt to do _please_ leave a possibility to disable
EOLConvertingInputStream
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
