Connected: An Internet Encyclopedia
RFC 1945 - 7.2.1 Type

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1945
Up: 7. Entity
Up: 7.2 Entity Body
Prev: 7.2 Entity Body
Next: 7.2.2 Length

### 7.2.1 Type

When an Entity-Body is included with a message, the data type of that body is determined via the header fields Content-Type and Content- Encoding. These define a two-layer, ordered encoding model:

           entity-body := Content-Encoding( Content-Type( data ) )

A Content-Type specifies the media type of the underlying data. A Content-Encoding may be used to indicate any additional content coding applied to the type, usually for the purpose of data compression, that is a property of the resource requested. The default for the content encoding is none (i.e., the identity function).

Any HTTP/1.0 message containing an entity body should include a Content-Type header field defining the media type of that body. If and only if the media type is not given by a Content-Type header, as is the case for Simple-Response messages, the recipient may attempt to guess the media type via inspection of its content and/or the name extension(s) of the URL used to identify the resource. If the media type remains unknown, the recipient should treat it as type "application/octet-stream".

Next: 7.2.2 Length

Connected: An Internet Encyclopedia
RFC 1945 - 7.2.1 Type