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
network
Click on the red underlined text to get to the source
... cache stores cachable responses in order to reduce the response
time and network bandwidth consumption on future, equivalent
requests. Any client or server may include a cache ...
... HTTP from being implemented on top of any other protocol on
the Internet, or on other networks. HTTP only presumes a reliable
transport ...
...
The "http" scheme is used to locate network resources via the HTTP
protocol. This section defines the scheme-specific syntax and
semantics ...
... entity-body in order to ensure "safe transport" through the network.
This differs from a content coding in that the transfer coding is a
property of the message, not of the original entity ...
... URI MUST be transmitted (see section 3.2.1, abs_path) as
the Request-URI, and the network location of the URI (net_loc) MUST
be transmitted in a Host ...
... used much more efficiently, with much lower elapsed time.
o Network congestion is reduced by reducing the number of packets
caused by TCP ...
... determine the congestion state of the network.
o HTTP can evolve more gracefully; since errors can be reported
...
... client or server does not detect
the other side's close promptly it could cause unnecessary resource
drain on the network.
A client ...
... connection in the
middle of transmitting a response, unless a network or client failure
is suspected.
...
... connections with the expectation that
clients will retry. The latter technique can exacerbate network
congestion.
...
... client sending a message-body SHOULD monitor
the network connection for an error status while it is transmitting
...
... header field(s). The
conditional GET method is intended to reduce unnecessary network
usage by allowing cached entities to be refreshed without requiring
multiple requests or transferring data already held by the client ...
... 14.36. The partial GET method is intended to reduce unnecessary
network usage by allowing partially-retrieved entities to be
completed without transferring data already held by the client.
...
... the request message or on other information pertaining to the request
(such as the network address of the client).
...
... capabilities from examining the request, and generally when public
caches are used to distribute server load and reduce network usage.
Agent ...
... to send requests in many cases, and to eliminate the need to send
full responses in many other cases. The former reduces the number of
network round-trips required for many operations; we use an
"expiration" mechanism for this purpose (see section 13.2). The
...
... round-trips required for many operations; we use an
"expiration" mechanism for this purpose (see section 13.2). The
latter reduces network bandwidth requirements; we use a "validation"
...
... caches along the path from the
origin server, plus the amount of time it has been in transit along
network paths.
We use the term "age_value" to denote the value of the Age header ...
... synchronization step.
Because of network-imposed delays, some significant interval may pass
from the time that a server generates a response and the time it is
received at the next outbound cache ...
... Because the request that resulted in the returned Age value must have
been initiated prior to that Age value's generation, we can correct
for delays imposed by the network by recording the time at which the
request was initiated. Then, when an Age value is received, it MUST
be interpreted relative to the time the request was initiated, not
...
... certain caches may violate this expectation (for example, when little
or no network connectivity is available). A client can usually detect
that such a response was taken from a cache ...
... HTTP/1.1, due to the difficulty of providing consistent
updates and the problems arising from server, cache, or network
failure prior to write-back.
...
... or compromised caches may not recognize or obey this directive; and
communications networks may be vulnerable to eavesdropping.
...
... min-fresh, max-stale, or max-age.
In some cases, such as times of extremely poor network connectivity,
a client may want a cache ...
... as described in section 3.2.2). The Host field value MUST represent
the network location of the origin server or gateway given by the
original URL ...
... Corrections for different time bases between client and server are at
best approximate due to network latency.
...
... possibly other than the contents of request-header fields (e.g., the
network address of the client), play a role ...
... Proxies and gateways used as a portal through a network firewall
SHOULD NOT, by default, forward the names and ports ...
... SHOULD be included if the cache is intentionally disconnected from
the rest of the network for a period of time.
13 Heuristic ...
... entity, which is
transmitted in clear text across the physical network used as the
carrier. HTTP does not prevent additional authentication ...
... password over
the physical network. It is this problem which Digest Authentication
attempts to address ...
... Proxies which serve as a portal through a network firewall SHOULD
take special precautions regarding the transfer of header information ...
... click-trails or form submissions of individual users. Note that for
many users not behind a proxy, the network address of the host
...
... HTTP clients do not observe this rule, they could be spoofed when
a previously-accessed server's IP address changes. As network
renumbering is expected to become increasingly common, the
possibility of this form of attack ...
... Berners-Lee, T., "Universal Resource Identifiers in WWW", A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web", RFC 1630, CERN, June 1994. ...
... Kantor, B., and P. Lapsley. "Network News Transfer Protocol." A Proposed Standard for the Stream-Based Transmission of News", RFC 977(-> 3977prop) ...
... Venkata N. Padmanabhan and Jeffrey C. Mogul. Improving HTTP Latency. Computer Networks and ISDN Systems, v. 28, pp. 25-35, Dec. 1995. Slightly revised version of paper in Proc. 2nd International WWW Conf. '94: Mosaic and the Web, Oct. 1994, which is available at http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/ ...
... Mills, D., "Network Time Protocol, Version 3, Specification, Implementation and Analysis", RFC 1305draft, University of Delaware, March 1992. ...