Connected: An Internet Encyclopedia
RFC 1945 - C.4 No Content-Transfer-Encoding

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1945
Up: C. Relationship to MIME
Prev: C.3 Introduction of Content-Encoding
Next: C.5 HTTP Header Fields in Multipart Body-Parts

### C.4 No Content-Transfer-Encoding

HTTP does not use the Content-Transfer-Encoding (CTE) field of RFC 1521. Proxies and gateways from MIME-compliant protocols to HTTP must remove any non-identity CTE ("quoted-printable" or "base64") encoding prior to delivering the response message to an HTTP client.

Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct format and encoding for safe transport on that protocol, where "safe transport" is defined by the limitations of the protocol being used. Such a proxy or gateway should label the data with an appropriate Content-Transfer-Encoding if doing so will improve the likelihood of safe transport over the destination protocol.

Next: C.5 HTTP Header Fields in Multipart Body-Parts

Connected: An Internet Encyclopedia
RFC 1945 - C.4 No Content-Transfer-Encoding