Connected: An Internet Encyclopedia
RFC 1945 - C.1 Conversion to Canonical Form

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1945
Up: C. Relationship to MIME
Prev: C. Relationship to MIME
Next: C.2 Conversion of Date Formats

### C.1 Conversion to Canonical Form

RFC 1521 requires that an Internet mail entity be converted to canonical form prior to being transferred, as described in Appendix G of RFC 1521 [5]. Section 3.6.1 of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP.

RFC 1521 requires that content with a Content-Type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted over HTTP.

Where it is possible, a proxy or gateway from HTTP to a strict RFC 1521 environment should translate all line breaks within the text media types described in Section 3.6.1 of this document to the RFC 1521 canonical form of CRLF. Note, however, that this may be complicated by the presence of a Content-Encoding and by the fact that HTTP allows the use of some character sets which do not use octets 13 and 10 to represent CR and LF, as is the case for some multi-byte character sets.

Next: C.2 Conversion of Date Formats

Connected: An Internet Encyclopedia
RFC 1945 - C.1 Conversion to Canonical Form