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
MIME
Click on the red underlined text to get to the source
... 1945 [6], improved
the protocol by allowing messages to be in the format of MIME-like
messages, containing metainformation about the data transferred and
modifiers on the request/response ...
... URI, and
protocol version, followed by a MIME-like message containing request
modifiers, client information, and possible body content over a
...
... version and a success or error code,
followed by a MIME-like message containing server information, entity
metainformation, and possible entity ...
... entity-body content. The relationship
between HTTP and MIME is described in appendix 19.4.
Most HTTP ...
... HTTP uses the same definition of the term "character set" as that
described for MIME:
The term "character set ...
... methods such as those that use ISO
2022's techniques. However, the definition associated with a MIME
character set name MUST fully specify the mapping to be performed
...
... referred to as a "character encoding." However, since HTTP and MIME
share the same registry, it is important that the terminology also
...
... Transfer codings are analogous to the Content-Transfer-Encoding
values of MIME , which were designed to enable safe transport of
binary data ...
... by the user agent) the parameters
for that MIME type as described by that type/subtype definition to
the and inform the user of any problems discovered.
...
...
MIME provides for a number of "multipart" types -- encapsulations of
one or more entities within a single message-body ...
... one or more entities within a single message-body. All multipart
types share a common syntax, as defined in MIME [7], and MUST
include a boundary parameter as part of the media type value ...
... CRLF to represent line breaks between body-parts. Unlike in MIME, the
epilogue of any multipart message MUST be empty; HTTP applications
...
... HTTP user agent SHOULD follow the same or similar
behavior as a MIME user agent would upon receipt of a multipart type.
If an application receives an unrecognized multipart subtype, the
...
...
Note: The meaning of this field is significantly different from the
corresponding definition in MIME, where it is an optional field
used within the "message/external-body" content-type ...
... HTTP extends RFC 1864draft to permit the digest to be computed for MIME
composite media-types ...
... entity-body for
composite types may contain many body-parts, each with its own MIME
and HTTP headers (including Content-MD5 ...
... entity-bodies. One is that
HTTP, unlike MIME, does not use Content-Transfer-Encoding, and does
use Transfer-Encoding ...
... HTTP
more frequently uses binary content types than MIME, so it is worth
noting that, in such cases, the byte order used to compute the
...
... example, a response to a request for multiple non-overlapping
ranges), these are transmitted as a multipart MIME message. The
multipart MIME content-type used for this purpose is defined in this
...
... ranges), these are transmitted as a multipart MIME message. The
multipart MIME content-type used for this purpose is defined in this
specification to be "multipart/byteranges". See appendix 19.2 for its
definition.
...
...
A client that cannot decode a MIME multipart/byteranges message
should not ask for multiple byte-ranges in a single request.
...
... 822std11(-> 2822prop). Similarly, it
reuses many of the definitions provided by Nathaniel Borenstein and
Ned Freed for MIME. We hope that their inclusion in this
specification will help reduce past confusion over the relationship
between HTTP ...
... Freed, N., and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045draft, Innosoft, First Virtual, November 1996. ...
... Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII ...
... example, a response to a request for multiple non-overlapping
ranges), these are transmitted as a multipart MIME message. The
multipart media type for this purpose is called
...
... Content-Type and Content-Range fields. The parts are
separated using a MIME boundary parameter.
Media Type name ...
... Differences Between HTTP Entities and MIME Entities ...
... Internet Mail (RFC
822) and the Multipurpose Internet Mail Extensions (MIME ) to allow
entities to be transmitted in an open variety of representations and
with extensible mechanisms. However, MIME ...
... MIME ) to allow
entities to be transmitted in an open variety of representations and
with extensible mechanisms. However, MIME [7] discusses mail, and
HTTP ...
... HTTP has a few features that are different from those described in
MIME. These differences were carefully chosen to optimize
performance over binary connections ...
... Proxies and gateways to strict MIME environments SHOULD be aware of
these differences and provide the appropriate conversions where
necessary. Proxies ...
... necessary. Proxies and gateways from MIME environments to HTTP also
need to be aware of the differences because some conversions may be
...
... media type
when transmitted over HTTP. MIME requires that content with a type of
"text" represent line breaks as CRLF ...
... proxy or gateway from HTTP to a strict MIME
environment SHOULD translate all line breaks within the text media
types ...
... 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 of CRLF ...
... proxies and gateways from HTTP to MIME-compliant protocols MUST
either change the value of the Content-Type ...
... function as Content-Encoding. However, this parameter is not part of
MIME.)
...
... Proxies and gateways from HTTP to MIME-compliant protocols are
responsible for ensuring that the message is in the correct format
and encoding ...
...
In MIME, most header fields in multipart body-parts are generally
ignored unless the field name begins with "Content-". In HTTP/1.1 ...
... gateways MUST remove any transfer coding prior to
forwarding a message via a MIME-compliant protocol.
A process for decoding the "chunked" transfer coding (section 3.6)
...
... MIME-Version ...
...
HTTP is not a MIME-compliant protocol (see appendix 19.4). However,
HTTP/1.1 messages may include a single MIME-Version ...
... MIME-compliant protocol (see appendix 19.4). However,
HTTP/1.1 messages may include a single MIME-Version general-header
field to indicate what version of the MIME ...
... MIME-Version general-header
field to indicate what version of the MIME protocol was used to
construct the message. Use of the MIME-Version header field ...
... version of the MIME protocol was used to
construct the message. Use of the MIME-Version header field indicates
that the message is in full compliance with the MIME ...
... MIME-Version header field indicates
that the message is in full compliance with the MIME protocol.
Proxies/gateways ...
... gateways are responsible for ensuring full compliance (where
possible) when exporting HTTP messages to strict MIME environments.
MIME-Version ...
... HTTP/1.1 message parsing and semantics are defined by this document
and not the MIME specification.
...