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
requirement
Click on the red underlined text to get to the source
... This specification defines the protocol referred to as "HTTP/1.1".
This protocol includes more stringent requirements than HTTP/1.0 in
order to ensure reliable implementation of its features.
...
... Requirements ...
... 1123std3 [8] for defining
the significance of each particular requirement. These words are:
MUST
...
... MUST
This word or the adjective "required" means that the item is an
absolute requirement of the specification.
SHOULD
...
...
An implementation is not compliant if it fails to satisfy one or more
of the MUST requirements for the protocols it implements. An
implementation that satisfies all the MUST and all the SHOULD
requirements ...
... requirements for the protocols it implements. An
implementation that satisfies all the MUST and all the SHOULD
requirements for its protocols is said to be "unconditionally
compliant"; one that satisfies all the MUST requirements but not all
...
... requirements for its protocols is said to be "unconditionally
compliant"; one that satisfies all the MUST requirements but not all
the SHOULD requirements for its protocols is said to be
...
... compliant"; one that satisfies all the MUST requirements but not all
the SHOULD requirements for its protocols is said to be
"conditionally compliant."
...
... proxy must implement
both the client and server requirements of this specification.
gateway
A ...
...
Not all responses are usefully cachable, and some requests may
contain modifiers which place special requirements on cache behavior.
HTTP ...
... cache behavior.
HTTP requirements for cache behavior and cachable responses are
defined in section 13.
...
...
Note: HTTP requirements for the date/time stamp format apply only
to their usage within the protocol stream ...
... the text line break. HTTP relaxes this requirement and allows the
transport of text media with plain CR ...
... Host header field value. (But see
section 19.5.1 for other requirements on Host support in HTTP/1.1.)
...
... connections through the same server. The use of persistent
connections places no requirements on the length of this time-out for
either the client or the server.
...
... Message Transmission Requirements ...
...
General requirements:
o HTTP/1.1 ...
... method allows the client to
determine the options and/or requirements associated with a resource,
or the capabilities of a server, without implying a resource action
or initiating a resource retrieval.
...
...
The response to a GET request is cachable if and only if it meets the
requirements for HTTP caching described in section 13.
...
... retrieve a cachable resource.
POST requests must obey the message transmission requirements set out
in section 8.2.
...
... origin server.
PUT requests must obey the message transmission requirements set out
in section 8.2.
...
... caches MUST recognize the Vary header field when it
is included in a response and obey the requirements described in
section 13.6 that describes the interactions between caching and
content negotiation ...
... "expiration" mechanism for this purpose (see section 13.2). The
latter reduces network bandwidth requirements; we use a "validation"
mechanism for this purpose (see section 13.3).
...
... mechanism for this purpose (see section 13.3).
Requirements for performance, availability, and disconnected
operation require us to be able to relax the goal of semantic ...
...
2. It is "fresh enough" (see section 13.2). In the default case, this
means it meets the least restrictive freshness requirement of the
client, server, and cache ...
... client, server, and cache (see section 14.9); if the origin server
so specifies, it is the freshness requirement of the origin server
alone.
...
... user
agent should explicitly indicate to the user whenever this results in
the display of information that might not meet the server's
transparency requirements (in particular, if the displayed entity is
known to be stale). Since the protocol normally allows the user agent ...
... function (see section 13.3.3).
If either requirement is not meant, the cache must use only the most
recent partial response (based on the Date values transmitted with
...
... to reply to the current request. It may insert it into cache storage
and may, if it meets all other requirements, use it to respond to any
future requests that would previously have caused the old response to
be returned. If it inserts the new response into cache ...
...
By default, a response is cachable if the requirements of the request
method, request header fields ...
... part of their normal operation.
The purpose of this directive is to meet the stated requirements of
certain users and service authors who are concerned about accidental
...
... HTTP/1.1-compliant cache may exploit the
requirement that the max-age directive overrides the Expires
header, and the fact that non-HTTP/1.1 ...
... to the behavior specified by the standard directive, and those that
understand the new directive will recognize it as modifying the
requirements associated with the standard directive. In this way,
extensions to the Cache-Control directives can be made without
...
...
For organizations that have strong privacy requirements for hiding
internal structures, a proxy MAY combine an ordered subsequence of
...
... possibility of this form of attack will grow. Observing this
requirement thus reduces this potential security vulnerability.
...
... security vulnerability.
This requirement also improves the load-balancing behavior of clients
for replicated servers using the same DNS name ...
... Sollins, K., and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, MIT ...
...
Although this document specifies the requirements for the generation
of HTTP/1.1 messages, not all applications will be correct in their
...
... ISO-8859-1.
Additional rules for requirements on parsing and encoding of dates
and other potential problems with date encodings ...
... existing HTTP/1.0 applications) correctly implement these
requirements:
o Both clients and servers ...
... version conflicts.
PATCH requests must obey the message transmission requirements set
out in section 8.2.
...