- age
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
The age of a response is the time since it was sent by, or successfully validated with, the origin server.
- cache
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion. A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel.A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests. The rules for determining the cacheability of HTTP responses are defined in section 13. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular request.
- cacheable
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests. The rules for determining the cacheability of HTTP responses are defined in section 13. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular request.
- client
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
A program that establishes connections for the purpose of sending requests.
- connection
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
A transport layer virtual circuit established between two programs for the purpose of communication.
- content negotiation
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
The mechanism for selecting the appropriate representation when servicing a request, as described in section 12. The representation of entities in any response can be negotiated (including error responses).
- entity
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
The information transferred as the payload of a request or response. An entity consists of metainformation in the form of entity-header fields and content in the form of an entity-body, as described in section 7.
- explicit expiration time
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.
- first-hand
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
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.
- fresh
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
A response is fresh if its age has not yet exceeded its freshness lifetime.
- freshness lifetime
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
The length of time between the generation of a response and its expiration time.
- gateway
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway.
- heuristic expiration time
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
An expiration time assigned by a cache when no explicit expiration time is available.
- inbound/outbound
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server", and "outbound" means "traveling toward the user agent"
- message
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
The basic unit of HTTP communication, consisting of a structured sequence of octets matching the syntax defined in section 4 and transmitted via the connection.
- origin server
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
The server on which a given resource resides or is to be created.
- proxy
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients. Requests are serviced internally or by passing them on, with possible translation, to other servers. A proxy MUST implement both the client and server requirements of this specification. A "transparent proxy" is a proxy that does not modify the request or response beyond what is required for proxy authentication and identification. A "non-transparent proxy" is a proxy that modifies the request or response in order to provide some added service to the user agent, such as group annotation services, media type transformation, protocol reduction, or anonymity filtering. Except where either transparent or non-transparent behavior is explicitly stated, the HTTP proxy requirements apply to both types of proxies.
- representation
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
An entity included with a response that is subject to content negotiation, as described in section 12. There may exist multiple representations associated with a particular response status.
- request
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
An HTTP request message, as defined in section 5.
- resource
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)
A network data object or service that can be identified by a URI, as defined in section 3.2. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or vary in other ways.