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
Proxies
Click on the red underlined text to get to the source
... HTTP/1.0 does
not sufficiently take into consideration the effects of hierarchical
proxies, caching, the need for persistent connections, and virtual
hosts. In addition, the proliferation of incompletely-implemented
...
... HTTP is also used as a generic protocol for communication between
user agents and proxies/gateways to other Internet systems, including
...
... A response is first-hand if it comes directly and without
unnecessary delay from the origin server, perhaps via one or more
proxies. A response is also first-hand if its validity has just
been checked directly with the origin server.
...
... architectures and configurations
of caches and proxies currently being experimented with or deployed
across the World Wide Web; these systems include national hierarchies
...
... represent the rel_path part of addresses, and HTTP proxies may
receive requests for URIs not defined by RFC 1738(-> 4266prop | 4248prop) ...
... HTTP
applications, as is sometimes the case when retrieving or posting
messages via proxies/gateways to SMTP or NNTP ...
... HTTP/1.1 clients will only generate
them in requests to proxies.
The most common form of Request-URI ...
... status code.
In requests that they forward, proxies MUST NOT rewrite the
"abs_path" part of a Request-URI in any way except as noted above to
...
... Implementers
should be aware that some pre-HTTP/1.1 proxies have been known to
rewrite the Request-URI.
...
... to be defined without changing the protocol, but these fields cannot
be assumed to be recognizable by the recipient. Unrecognized header
fields SHOULD be ignored by the recipient and forwarded by proxies.
...
...
It is especially important that proxies correctly implement the
properties of the Connection header field ...
...
This means that clients, servers, and proxies MUST be able to recover
from asynchronous close events. Client software ...
... client to limit the
length of the request chain, which is useful for testing a chain of
proxies forwarding messages in an infinite loop.
If successful, the response SHOULD contain the entire request message ...
... mechanisms are not defined by this specification.
Proxies MUST be completely transparent regarding user agent
authentication ...
...
For the purpose of defining the behavior of caches and non-caching
proxies, we divide HTTP headers into two categories:
...
... response without needing to revalidate it (since it has already been
authenticated once by that user), while still requiring proxies that
service many users to revalidate each time (in order to make sure
...
... Implementers of intermediate caches (proxies) have found it useful to
convert the media type of certain entity ...
... options that are desired for that particular connection and MUST NOT
be communicated by proxies over further connections.
...
... servers may generate the Content-MD5 header field; proxies and
gateways MUST NOT generate it, as this would defeat its value as an
...
... entity-body,
including gateways and proxies, MAY check that the digest value in
this header field matches that of the entity ...
... TRACE
method (section 14.31) to limit the number of proxies or gateways
that can forward the request to the next inbound server. This can be
...
... the Proxy-Authenticate field. When multiple proxies are used in a
chain, the Proxy-Authorization ...
... client request to the next proxy if
that is the mechanism by which the proxies cooperatively authenticate
a given request.
...
... The Via general-header field MUST be used by gateways and proxies to
indicate the intermediate protocols and recipients between the user
agent and the server on requests, and between the origin server and
...
... Via: 1.0 fred, 1.1 nowhere.com (Apache/1.1)
Proxies and gateways used as a portal through a network ...
... header field a configurable option.
Proxies which serve as a portal through a network firewall ...
... running the user agent will also serve as a long-lived user
identifier. In environments where proxies are used to enhance
privacy, user agents ...
... configuration options to end users. As an extreme privacy measure,
proxies could filter the accept headers in relayed requests. General
...
... MIME environments SHOULD be aware of
these differences and provide the appropriate conversions where
necessary. Proxies and gateways from MIME environments to HTTP ...
... HTTP/1.1 uses a restricted set of date formats (section 3.3.1) to
simplify the process of date comparison. Proxies and gateways from
other protocols SHOULD ensure that any Date header field ...
... Encoding header field. Since this acts as a modifier on the media
type, proxies and gateways from HTTP to MIME-compliant ...
... Content-Transfer-Encoding (CTE) field of MIME.
Proxies and gateways from MIME-compliant protocols to HTTP ...
... Transfer-Encoding header field (section
14.40). Proxies/gateways MUST remove any transfer coding prior to
...
... that the message is in full compliance with the MIME protocol.
Proxies/gateways are responsible for ensuring full compliance (where
possible) when exporting HTTP messages ...
... clients must be prevented from
using Keep-Alive when talking to proxies.
However, talking to proxies ...
... proxies.
However, talking to proxies is the most important use of persistent
connections, so that prohibition is clearly unacceptable. Therefore,
...