Glossary of "Hypertext Transfer Protocol -- HTTP/1.1"

Term entries in the "Hypertext Transfer Protocol -- HTTP/1.1" glossary

W3C Glossaries

Showing results 21 - 29 of 29

response

From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)

An HTTP response message, as defined in section 6.

semantically transparent

From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)

A cache behaves in a "semantically transparent" manner, with respect to a particular response, when its use affects neither the requesting client nor the origin server, except to improve performance. When a cache is semantically transparent, the client receives exactly the same response (except for hop-by-hop headers) that it would have received had its request been handled directly by the origin server.

server

From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)

An application program that accepts connections in order to service requests by sending back responses. Any given program may be capable of being both a client and a server; our use of these terms refers only to the role being performed by the program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request.

stale

From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)

A response is stale if its age has passed its freshness lifetime.

tunnel

From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)

An intermediary program which is acting as a blind relay between two connections. Once active, a tunnel is not considered a party to the HTTP communication, though the tunnel may have been initiated by an HTTP request. The tunnel ceases to exist when both ends of the relayed connections are closed.

upstream/downstream

From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)

Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.

user agent

From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)

The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user tools.

validator

From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)

A protocol element (e.g., an entity tag or a Last-Modified time) that is used to find out whether a cache entry is an equivalent copy of an entity.

variant

From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15)

A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations is termed a `varriant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.

View another glossary