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
clients and server
Click on the red underlined text to get to the source
... 12] date format and lacks a four-digit year.
HTTP/1.1 clients and servers that parse the date value MUST accept
all three formats (for compatibility with HTTP/1.0 ...
... date/time stamp format apply only
to their usage within the protocol stream. Clients and servers are
not required to use these formats for user presentation, request
logging, etc.
...
... tokens should be registered; to allow
interoperability between clients and servers, specifications of the
content coding algorithms needed to implement a new value should be
...
... connection.
Clients and servers SHOULD NOT assume that a persistent connection is
maintained for HTTP ...
... client or server wishes to time-out it SHOULD issue a graceful
close on the transport connection. Clients and servers SHOULD both
constantly watch for the other side of the transport close, and
...
... methods cannot be assumed to
share the same semantics for separately extended clients and servers.
The Host ...
...
Some clients and servers may wish to be compatible with some previous
implementations of persistent connections in HTTP/1.0 ...
... implementations of persistent connections in HTTP/1.0 clients and
servers. Persistent connections in HTTP/1.0 must be explicitly
...