HTTP
Click on the red underlined text to get to the source
... proxy, origin server, and
http_URL have the same meaning as in the HTTP/1.1 specification
[RFC2616]. The terms abs_path and absoluteURI have the same meaning
...
... port)
and abs_path portions of the absoluteURI (http_URL) of the HTTP
request line. Note that request-host is a HN.
...
... port portion of the absoluteURI
(http_URL) of the HTTP request line. If the absoluteURI has no
explicit port, the request-port ...
... This document describes a way to create stateful sessions with HTTP
requests and responses. Currently, HTTP servers respond to each
client request ...
... create stateful sessions with HTTP
requests and responses. Currently, HTTP servers respond to each
client request without relating that request to previous or
...
... state management mechanism allows clients
and servers that wish to exchange state information to place HTTP
requests and responses within a larger context, which we term a
"session ...
... state
information to the origin server. The goal is to have a minimal
impact on HTTP and user agents.
...
... space characters),
and http_URL from the HTTP/1.1 specification [RFC2616] to describe
their syntax.
...
... calculate the age of the cookie according to the age calculation
rules in the HTTP/1.1 specification [RFC2616]. When the age is
greater than delta-seconds seconds, the client ...
...
The origin server SHOULD send the following additional HTTP/1.1
response headers, depending on circumstances:
...
...
HTTP/1.1 servers MUST send Expires: old-date (where old-date is a
date long in the past) on responses containing Set-Cookie2 response
...
... headers unless they know for certain (by out of band means) that
there are no HTTP/1.0 proxies in the response chain. HTTP/1.1
...
... there are no HTTP/1.0 proxies in the response chain. HTTP/1.1
servers MAY send other Cache-Control directives that permit caching
...
... servers MAY send other Cache-Control directives that permit caching
by HTTP/1.1 proxies in addition to the Expires: old-date directive;
the Cache-Control ...
... Caching and HTTP/1.0 ...
... headers, because there was no
mechanism to suppress caching of headers prior to HTTP/1.1. This
caching can lead to security problems. Documents transmitted by an
...
... cache documents (following Expires:
<a date in the past> or Pragma: no-cache (HTTP/1.0), or Cache-
control: no-cache ...
... Cache-
control: no-cache (HTTP/1.1)) uncachable documents present no
problem. However, pre-expired documents may be stored in caches.
...
...
This document really represents the collective efforts of the HTTP
Working Group of the IETF ...
... Kristol, D.M., "Proposed HTTP State-Info Mechanism", available at <http://portal.research.bell-labs.com/~dmk/state-info.html>, September, 1995. ...
... "Persistent Client State -- HTTP Cookies", available at <http://www.netscape.com/newsref/std/cookie_spec.html>, undated. ...
... Kristol, D. and L. Montulli, "HTTP State Management Mechanism", RFC 2109(-> 2965prop), February 1997. ...
... Fielding, R., Gettys, J., Mogul, J., Frystyk, H. and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616draft, June 1999. ...