I am looking at TS-466 (Multiline headers are not preserved) and as far as I
can tell this is by design. The field parser in MIME.cc goes to some effort to
detect this situation and then strip out the intervening whitespace, including
the CR/LF. So something like
Accept: text/html,
text
A wild guess would be that some clients in the bad old days did not handle it
right. We should obey the protocol IMO, possibly with having an option to
enable this non-compliant behavior per transaction.
-- leif
Ps
Logan airport sucks, that's all... ;)
On Aug 11, 2011, at 2:07 PM, "Alan M. Ca
