HTTP Response Headers
(Page 1 of 2)
The counterpart to request headers, response headers appear only in HTTP responses sent by servers or intermediaries. They provide additional data that expands upon the summary information that is present in the status line at the beginning of each server reply. Many of the response headers are sent only in response to the receipt of specific types of requests, or even particular headers within certain requests.
There are nine response headers defined for HTTP/1.1.
Tells the client whether or not the server accepts partial content requests using the Range request header, and if so, what type. Typical examples include Accept-Range: bytes if the server accepts byte ranges, or Accept-Range: none if range requests are not supported.
Tells the client the approximate age of the resource, as calculated by the device sending the response.
Specifies the entity tag for the entity included in the response. This value can be used by the client in future requests to uniquely identify an entity, using the If-Match request header or similar.
Indicates a new URL that the server is instructing the client to use in place of the one the client initially requested. This header is normally used when the server redirects a client request to a new location, using a 301, 302 or 307 reply. It is also used to indicate the location of a created resource in a 201 (Created) response to a PUT request.
Note that this is not the same as the Content-Location entity header, which is used to indicate the location of the originally-requested resource.
Home - Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.