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
sender
Click on the red underlined text to get to the source
... versions
of the protocol. The protocol versioning policy is intended to allow
the sender to indicate the format of a message and its capacity for
understanding further HTTP communication, rather than the features
...
... algorithm, but which may add to the message semantics and imply
additional capabilities of the sender. The <major> number is
incremented when the format of a message within the protocol is
changed.
...
... Since the protocol version indicates the protocol capability of the
sender, a proxy/gateway MUST never send a message with a version ...
... character set (section 3.4) of the data. When no explicit charset
parameter is provided by the sender, media subtypes of the "text"
type are defined to have a default charset value of "ISO ...
... charset parameter incorrectly to mean "recipient should guess."
Senders wishing to defeat this behavior MAY include a charset
parameter even when the charset is ISO ...
... HTTP/1.1 recipients MUST respect the
charset label provided by the sender; and those user agents that have
a provision to "guess" a charset ...
... self-delimiting, then that defines the length. This media type MUST
NOT be used unless the sender knows that the recipient can parse it;
the presence in a request of a Range header ...
... headers.
In this section, both sender and recipient refer to either the client
or the server, depending on who sends and who receives the entity ...
... between caches. The Age header value is the sender's estimate of the
amount of time since the response was generated at the origin server.
In the case of a cached response that has been revalidated with the
...
... header fields. For entity-header fields, both sender and
recipient refer to either the client or the server, depending on who
...
...
The Age response-header field conveys the sender's estimate of the
amount of time since the response (or its revalidation) was generated
at the origin server. A cached response is "fresh" if its age does
...
... The Connection general-header field allows the sender to specify
options that are desired for that particular connection and MUST NOT
...
... HTTP/1.1 defines the "close" connection option
for the sender to signal that the connection will be closed after
completion of the response. For example,
...
... Language is specified, the default is that the content
is intended for all language audiences. This may mean that the sender
does not consider it to be specific to any natural language ...
... does not consider it to be specific to any natural language, or that
the sender does not know for which language it is intended.
...
... type of transformation has been applied to the message body in order
to safely transfer it between the sender and the recipient. This
differs from the Content-Encoding in that the transfer coding is a
...
... 822std11(-> 2822prop) and is intended to be used for tracking message forwards,
avoiding request loops, and identifying the protocol capabilities of
all senders along the request/response chain.
...
... tag of the resource from which the enclosed entity was
derived before modifications were made by the sender. This field is
used to help manage the process of merging successive changes to a
resource, particularly when such changes are being made in parallel
...