On Thursday, April 3, 2003, at 04:58 PM, Stipe Tolj wrote:
Paul Keogh wrote:
My understanding is that the MIME RFCs specify a canonical encoding of a "blank line" or separator of <cr><lf>. The obvious use of this is to get around differences across operating systems in this regard. (Think UNIX vs. Microsoft).
So accepting a <lf> as a MIME separator may well get you over the problem of a broken peer implementation but it will potentially cause problems elsewhere. So, as Aarno suggests, if you need to break MIME functionality, you should have to explicitly turn it on, in the full knowledge of what you are doing. It should not go into the code base as a default behaviour.
ok, as Paul vetoes for this, I'm also for a config directive.
Aarno, can you add the
strict-mime-parsing = [yes|no]
Yep, though i thought something like legal/broken.
as boolean config directive and make it default to yes, hence leaving the existing behaviour?
Yep
To which group should this go? wapbox?
To ppg core, i think, because ppg does the parsing.
Aarno
