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
encoding
Click on the red underlined text to get to the source
...
Characters other than those in the "reserved" and "unsafe" sets (see
section 3.2) are equivalent to their ""%" HEX HEX" encodings.
For example, the following three URIs ...
... provide more than one sequence of octets to represent a particular
character. This definition is intended to allow various kinds of
character encodings, from simple single-table mappings such as US-
ASCII to complex table switching methods ...
... Note: This use of the term "character set" is more commonly
referred to as a "character encoding." However, since HTTP and MIME
...
...
Content coding values indicate an encoding transformation that has
been or can be applied to an entity. Content codings are primarily
...
... case-insensitive. HTTP/1.1 uses
content-coding values in the Accept-Encoding (section 14.3) and
Content-Encoding (section 14.12) header fields ...
... content-coding values in the Accept-Encoding (section 14.3) and
Content-Encoding (section 14.12) header fields. Although the value
describes the content-coding, what is more important is that it
...
... indicates what decoding mechanism will be required to remove the
encoding.
The Internet Assigned Numbers Authority ...
... LZW).
Note: Use of program names for the identification of encoding
formats is not desirable and should be discouraged for future
encodings ...
... encoding
formats is not desirable and should be discouraged for future
encodings. Their use here is representative of historical practice,
not good design. For compatibility with previous implementations of
...
...
Transfer coding values are used to indicate an encoding
transformation that has been, can be, or may need to be applied to an
entity ...
... case-insensitive. HTTP/1.1 uses
transfer coding values in the Transfer-Encoding header field (section
14.40).
...
... 14.40).
Transfer codings are analogous to the Content-Transfer-Encoding
values of MIME , which were designed to enable safe transport ...
... transport.
The chunked encoding modifies the body of a message in order to
transfer it as a series of chunks, each with its own size indicator,
followed by an optional footer containing entity ...
... header
The chunked encoding is ended by a zero-sized chunk followed by the
footer, which is terminated by an empty line. The purpose of the
footer is to provide an efficient way to supply information about an
...
...
If an entity-body is encoded with a Content-Encoding, the underlying
data MUST be in a form defined above prior to being encoded.
...
... differs from the entity-body only when a transfer coding has been
applied, as indicated by the Transfer-Encoding header field (section
14.40).
...
... Transfer-Encoding>
Transfer-Encoding MUST be used to indicate any transfer codings
applied by an application to ensure safe and proper transfer of the
message. Transfer-Encoding ...
... Transfer-Encoding MUST be used to indicate any transfer codings
applied by an application to ensure safe and proper transfer of the
message. Transfer-Encoding is a property of the message, not of the
entity, and thus can be added or removed ...
... message-body in a request is signaled by the
inclusion of a Content-Length or Transfer-Encoding header field in
the request's message-headers ...
... message.
2. If a Transfer-Encoding header field (section 14.40) is present and
indicates that the "chunked" transfer coding has been applied, then
...
... indicates that the "chunked" transfer coding has been applied, then
the length is defined by the chunked encoding (section 3.6).
3. If a Content-Length ...
... | Date ; Section 14.19
| Pragma ; Section 14.32
| Transfer-Encoding ; Section 14.40
| Upgrade ; Section 14.41
| Via ; Section 14.44
...
... | Accept-Charset ; Section 14.2
| Accept-Encoding ; Section 14.3
| Accept-Language ; Section 14.4
...
... | Content-Base ; Section 14.11
| Content-Encoding ; Section 14.12
| Content-Language ; Section 14.13
...
... entity-body (if any) sent with an HTTP request or response is in
a format and encoding defined by the entity-header fields.
...
... entity-body is obtained
from the message-body by decoding any Transfer-Encoding that may have
been applied to ensure safe and proper transfer of the message.
...
... header fields Content-Type and Content-
Encoding. These define a two-layer, ordered encoding model:
...
... Content-Type specifies the media type of the underlying data.
Content-Encoding may be used to indicate any additional content
codings applied to the data, usually for the purpose of data
compression ...
... compression, that are a property of the requested resource. There is
no default encoding.
Any HTTP/1.1 ...
... immediately cease transmitting the body. If the body is being sent
using a "chunked" encoding (section 3.6), a zero length chunk and
empty footer MAY be used to prematurely mark the end of the
message. If the body was preceded by a Content-Length ...
... header fields (Accept,
Accept-Language, Accept-Encoding, etc.) which describe its
preferences for such a response.
...
... capabilities and user preferences: Accept (section 14.1), Accept-
Charset (section 14.2), Accept-Encoding (section 14.3), Accept-
Language (section 14.4), and User-Agent ...
... negotiation is advantageous when the response would vary
over commonly-used dimensions (such as type, language, or encoding),
when the origin server is unable to determine a user agent's
...
... Control directive, or in any request:
o Content-Encoding
o Content-Length
...
... Accept-Encoding ...
...
The Accept-Encoding request-header field is similar to Accept, but
restricts the content-coding values (section 14.12) which are
...
... gzip
If no Accept-Encoding header is present in a request, the server MAY
assume that the client will accept any content coding. If an Accept-
...
... assume that the client will accept any content coding. If an Accept-
Encoding header is present, and if the server cannot send a response
which is acceptable according to the Accept-Encoding header, then the
...
... Encoding header is present, and if the server cannot send a response
which is acceptable according to the Accept-Encoding header, then the
server SHOULD send an error response with the 406 (Not Acceptable)
...
... status code.
An empty Accept-Encoding value indicates none are acceptable.
...
... Content-Encoding ...
... referenced by the Content-Type header field. Content-Encoding is
primarily used to allow a document to be compressed without losing
the identity ...
...
Content-Encoding = "Content-Encoding" ":" 1#content-coding
Content codings are defined in section 3.5. An example of its use is
...
... Content codings are defined in section 3.5. An example of its use is
Content-Encoding: gzip
...
... Request-URI. Typically, the entity-body is stored with this
encoding and is only decoded before rendering or analogous usage.
If multiple encodings ...
... encoding and is only decoded before rendering or analogous usage.
If multiple encodings have been applied to an entity, the content
codings MUST be listed in the order in which they were applied.
...
... codings MUST be listed in the order in which they were applied.
Additional information about the encoding parameters MAY be provided
by other entity-header fields ...
... the request has a valid Content-Length field, uses Transfer-Encoding:
chunked or a multipart body.
...
... MD5 digest is computed based on the content of the entity-body,
including any Content-Encoding that has been applied, but not
including any Transfer-Encoding that may have been applied to the
...
... including any Content-Encoding that has been applied, but not
including any Transfer-Encoding that may have been applied to the
message-body. If the message is received with a Transfer-Encoding ...
... Transfer-Encoding that may have been applied to the
message-body. If the message is received with a Transfer-Encoding,
that encoding must be removed ...
... message-body. If the message is received with a Transfer-Encoding,
that encoding must be removed prior to checking the Content-MD5 value
...
... entity-body exactly as, and in the order that, they would be sent if
no Transfer-Encoding were being applied.
HTTP ...
... and HTTP headers (including Content-MD5, Content-Transfer-Encoding,
and Content-Encoding headers ...
... Content-MD5, Content-Transfer-Encoding,
and Content-Encoding headers). If a body-part has a Content-
Transfer-Encoding ...
... Content-Encoding headers). If a body-part has a Content-
Transfer-Encoding or Content-Encoding header, it is assumed that
...
... headers). If a body-part has a Content-
Transfer-Encoding or Content-Encoding header, it is assumed that
the content of the body-part has had the encoding ...
... Content-Encoding header, it is assumed that
the content of the body-part has had the encoding applied, and the
body-part is included in the Content-MD5 digest as is -- i.e.,
...
... body-part is included in the Content-MD5 digest as is -- i.e.,
after the application. The Transfer-Encoding header field is not
allowed within body-parts.
...
... HTTP, unlike MIME, does not use Content-Transfer-Encoding, and does
use Transfer-Encoding and Content-Encoding ...
... MIME, does not use Content-Transfer-Encoding, and does
use Transfer-Encoding and Content-Encoding. Another is that HTTP
...
... Content-Transfer-Encoding, and does
use Transfer-Encoding and Content-Encoding. Another is that HTTP
more frequently uses binary content types ...
... client
should consider unsynchronized clocks and rounding problems due to
the different encodings of time between the client and server. This
includes the possibility of race conditions if the document has
...
... Transfer-Encoding ...
...
The Transfer-Encoding general-header field indicates what (if any)
type of transformation has been applied to the message body ...
... to safely transfer it between the sender and the recipient. This
differs from the Content-Encoding in that the transfer coding is a
property of the message, not of the entity.
...
...
Transfer-Encoding = "Transfer-Encoding" ":" 1#transfer-
coding
...
... Transfer codings are defined in section 3.6. An example is:
Transfer-Encoding: chunked
Many older HTTP/1.0 ...
... Many older HTTP/1.0 applications do not understand the Transfer-
Encoding header.
...
... proxy if it applies any
transformation changing the content-coding (as specified in the
Content-Encoding header) or media-type (as specified in the
...
... line of the body.
Encoding considerations: only "7bit", "8bit", or "binary" are
permitted
...
... Optional parameters: none
Encoding considerations: only "7bit", "8bit", or "binary" are
permitted
...
...
Additional rules for requirements on parsing and encoding of dates
and other potential problems with date encodings include:
...
... requirements on parsing and encoding of dates
and other potential problems with date encodings include:
o HTTP/1.1 ...
... canonical form of CRLF. Note, however, that this may be complicated
by the presence of a Content-Encoding and by the fact that HTTP
...
... Introduction of Content-Encoding ...
... MIME does not include any concept equivalent to HTTP/1.1's Content-
Encoding header field. Since this acts as a modifier on the media
type, proxies and gateways ...
... media-type
parameter of ";conversions=<content-coding>" to perform an equivalent
function as Content-Encoding. However, this parameter is not part of
MIME.)
...
... No Content-Transfer-Encoding ...
... identity CTE ("quoted-printable" or "base64") encoding
prior to delivering the response message to an HTTP client ...
... 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 ...
... 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 ...
... Introduction of Transfer-Encoding ...