1 - 2 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W - X
media type
Click on the red underlined text to get to the source
... tolerant applications). The end-of-line marker within an entity-body
is defined by its associated media type, as described in section 3.7.
CRLF ...
... used to allow a document to be compressed or otherwise usefully
transformed without losing the identity of its underlying media type
and without loss of information. Frequently, the entity is stored in
...
... Media Types ...
... HTTP uses Internet Media Types in the Content-Type (section 14.18)
and Accept (section 14.1) header fields ...
...
Note: some older HTTP applications do not recognize media type
parameters. When sending data to older HTTP applications,
implementations should only use media type parameters ...
... media type
parameters. When sending data to older HTTP applications,
implementations should only use media type parameters when they are
required by that type/subtype definition.
...
... Media-type values are registered with the Internet Assigned Number
Authority (IANA). The media type registration process is outlined in
RFC 2048(-> 4289 | 4288) [17 ...
...
The "charset" parameter is used with some media types to define the
character set (section 3.4) of the data. When no explicit charset
parameter ...
... MIME [7], and MUST
include a boundary parameter as part of the media type value. The
message body is itself a protocol element ...
... message-body.
4. If the message uses the media type "multipart/byteranges", which is
self-delimiting, then that defines the length. This media type MUST
...
... 4. If the message uses the media type "multipart/byteranges", which is
self-delimiting, then that defines the length. This media type MUST
NOT be used unless the sender knows that the recipient can parse it;
...
... | "414" ; Request-URI Too Large
| "415" ; Unsupported Media Type
| "500" ; Internal Server Error
| "501" ; Not Implemented
...
...
Content-Type specifies the media type of the underlying data.
Content-Encoding may be used to indicate any additional content
...
... 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 field defining the media type of that body. If
and only if the media type is not given by a Content-Type field, the
recipient MAY attempt to guess the media type ...
... media type is not given by a Content-Type field, 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
...
... 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".
...
... user agent can choose the one most appropriate. The
entity format is specified by the media type given in the Content-
Type header field. Depending upon the format and the capabilities of
...
... user agent can choose the one most
appropriate. The entity format is specified by the media type given
in the Content-Type header field ...
... Unsupported Media Type ...
... Note: This is not called "format negotiation" because the alternate
representations may be of the same media type, but use different
capabilities of that type, be in different languages, etc.
...
...
The Accept request-header field can be used to specify certain media
types which are acceptable for the response. Accept headers can be
used to indicate that the request is specifically limited to a small
...
...
The asterisk "*" character is used to group media types into ranges,
with "*/*" indicating all media types ...
... media types into ranges,
with "*/*" indicating all media types and "type/*" indicating all
subtypes of that type. The media-range MAY include media type
parameters ...
... media types and "type/*" indicating all
subtypes of that type. The media-range MAY include media type
parameters that are applicable to that range.
...
... default value is q=1.
Note: Use of the "q" parameter name to separate media type
parameters from Accept extension parameters is due to historical
practice. Although this prevents any media type parameter named
...
... Note: Use of the "q" parameter name to separate media type
parameters from Accept extension parameters is due to historical
practice. Although this prevents any media type parameter named
"q" from being used with a media range, such an event is believed
...
... to be unlikely given the lack of any "q" parameters in the IANA
media type registry and the rare usage of any media type parameters
in Accept. Future media types ...
... IANA
media type registry and the rare usage of any media type parameters
in Accept. Future media types should be discouraged from
...
... media type registry and the rare usage of any media type parameters
in Accept. Future media types should be discouraged from
registering any parameter named "q".
...
... header field is present, then it is assumed that the
client accepts all media types. If an Accept header field is present,
and if the server cannot send a response which is acceptable
...
...
Verbally, this would be interpreted as "text/html and text/x-c are
the preferred media types, but if they do not exist, then send the
text/x-dvi entity, and if that does not exist, send the text/plain ...
... ranges can be overridden by more specific media ranges or
specific media types. If more than one media range applies to a given
type, the most specific reference has precedence. For example,
...
... 4) */*
The media type quality factor associated with a given type is
determined by finding the media range with the highest precedence
...
... caches (proxies) have found it useful to
convert the media type of certain entity bodies. A proxy might, for
...
... primarily used to allow a document to be compressed without losing
the identity of its underlying media type.
Content-Encoding ...
...
Content-Language may be applied to any media type -- it is not
limited to textual documents.
...
... Applications SHOULD use this field to indicate the size of the
message-body to be transferred, regardless of the media type of the
entity. It must be possible for the recipient to reliably determine
...
... Content-Type entity-header field indicates the media type of the
entity-body sent to the recipient or, in the case of the HEAD method ...
... entity-body sent to the recipient or, in the case of the HEAD method,
the media type that would have been sent had the request been a GET.
Content-Type ...
... Content-Type" ":" media-type
Media types are defined in section 3.7. An example of the field is
Content-Type ...
... Further discussion of methods for identifying the media type of an
entity is provided in section 7.2.1.
...
... Postel, J., "Media Type Registration Procedure", RFC 2048(-> 4289 | 4288), USC/ISI, November 1996. ...
... Internet Media Type message/http ...
... HTTP/1.1 protocol, this document serves
as the specification for the Internet media type "message/http". The
following is to be registered with IANA.
...
... Internet Media Type multipart/byteranges ...
... ranges), these are transmitted as a multipart MIME message. The
multipart media type for this purpose is called
"multipart/byteranges".
...
... "multipart/byteranges".
The multipart/byteranges media type includes two or more parts, each
with its own Content-Type and Content-Range ...
... performance over binary connections, to allow greater freedom in the
use of new media types, to make date comparisons easier, and to
acknowledge the practice of some early HTTP servers and clients ...
... entity be converted to canonical
form prior to being transferred. Section 3.7.1 of this document
describes the forms allowed for subtypes of the "text" media type
when transmitted over HTTP. MIME ...
... MIME
environment SHOULD translate all line breaks within the text media
types described in section 3.7.1 of this document to the MIME
canonical form ...
... HTTP/1.1's Content-
Encoding header field. Since this acts as a modifier on the media
type, proxies and gateways from HTTP ...
... Request-URI and the desired content of the resource
after the PATCH action has been applied. The list of differences is
in a format defined by the media type of the entity (e.g.,
"application/diff") and MUST include sufficient information to allow
...