blank.gif (43 bytes)

Church Of The
Swimming Elephant

C.3 Introduction of Content-Encoding Connected: An Internet Encyclopedia
C.3 Introduction of Content-Encoding

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1945
Up: C. Relationship to MIME
Prev: C.2 Conversion of Date Formats
Next: C.4 No Content-Transfer-Encoding

C.3 Introduction of Content-Encoding

C.3 Introduction of Content-Encoding

RFC 1521 does not include any concept equivalent to HTTP/1.0's Content-Encoding header field. Since this acts as a modifier on the media type, proxies and gateways from HTTP to MIME-compliant protocols must either change the value of the Content-Type header field or decode the Entity-Body before forwarding the message. (Some experimental applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=<content-coding>" to perform an equivalent function as Content-Encoding. However, this parameter is not part of RFC 1521.)

Next: C.4 No Content-Transfer-Encoding

Connected: An Internet Encyclopedia
C.3 Introduction of Content-Encoding


Protect yourself from cyberstalkers, identity thieves, and those who would snoop on you.
Stop spam from invading your inbox without losing the mail you want. We give you more control over your e-mail than any other service.
Block popups, ads, and malicious scripts while you surf the net through our anonymous proxies.
Participate in Usenet, host your web files, easily send anonymous messages, and more, much more.
All private, all encrypted, all secure, all in an easy to use service, and all for only $5.95 a month!

Service Details

Have you gone to church today?
All pages ©1999, 2000, 2001, 2002, 2003 Church of the Swimming Elephant unless otherwise stated
Church of the Swimming Elephant©1999, 2000, 2001, 2002, 2003 is a wholly owned subsidiary of Packetderm, LLC.

Packetderm, LLC
210 Park Ave #308
Worcester, MA 01609