see below
Mariano Absatz wrote:
El 9 May 2001, a las 9:51, Charles Lindsey escribió:
<SNIP>
that is, even
if the canonicalization was done improperly, the MD5 needs to be
computed over the form of the body part that exists *after*
canonicalization and *prior* to any content-transfer-encoding.
Yes, but the content-transfer-encoding provides a second opportunity to
canonicalize LF into CRLF (the encoding engine is likely separate from the
Copntent-MD5 engine) and so may introduce some CRLFs not appropriate for
that application type, and strange things may then arise upon upcoding.
I think the only safe way is to encode all CRLF in application types as
=0D=0A, giving
foo=0Dbar=0Abax=0D=0A=CRLF
Do you mean doing this for EVERY time you use CTE=QP or only for Content-
MD5?
This should not be done for CTE=QP for text/* content types.
This >>SHOULD<< be done EVERY TIME for CTE=QP for all anything/else
(non-text/*) content types.
Tony Hansen
tony(_at_)att(_dot_)com