Response Header Fields


Defines

#define HEADER_ACCEPT_RANGES   "Accept-Ranges"
#define HEADER_AGE   "Age"
#define HEADER_EXTENSION_TAG   "ETag"
#define HEADER_LOCATION   "Location"
#define HEADER_PROXY_AUTHENTICATE   "Proxy-Authenticate"
#define HEADER_RETRY_AFTER   "Retry-After"
#define HEADER_SERVER   "Server"
#define HEADER_VARY   "Vary"
#define HEADER_WWW_AUTHENTICATE   "WWW-Authenticate"

Detailed Description

The response-header fields allow the server to pass additional information about the response which cannot be placed in the Status-Line. These header fields give information about the server and about further access to the resource identified by the Request-URI. (see RFC 2616)

See also:
http://www.ietf.org/rfc/rfc2616.txt

Define Documentation

#define HEADER_ACCEPT_RANGES   "Accept-Ranges"
 

The Accept-Ranges response-header field allows the server to indicate its acceptance of range requests for a resource

Definition at line 45 of file nanohttp-response.h.

#define HEADER_AGE   "Age"
 

The Age response-header field conveys the sender's estimate of the amount of time since the response (or its revalidation) was generated at the origin server. A cached response is "fresh" if its age does not exceed its freshness lifetime.

Definition at line 55 of file nanohttp-response.h.

#define HEADER_EXTENSION_TAG   "ETag"
 

The ETag response-header field provides the current value of the entity tag for the requested variant. The headers used with entity tags are described in RFC 2616 sections 14.24, 14.26 and 14.44. The entity tag MAY be used for comparison with other entities from the same resource

See also:
http://www.ietf.org/rfc/rfc/2616.txt

Definition at line 67 of file nanohttp-response.h.

#define HEADER_LOCATION   "Location"
 

The Location response-header field is used to redirect the recipient to a location other than the Request-URI for completion of the request or identification of a new resource. For 201 (Created) responses, the Location is that of the new resource which was created by the request. For 3xx responses, the location SHOULD indicate the server's preferred URI for automatic redirection to the resource. The field value consists of a single absolute URI.

Definition at line 80 of file nanohttp-response.h.

#define HEADER_PROXY_AUTHENTICATE   "Proxy-Authenticate"
 

The Proxy-Authenticate response-header field MUST be included as part of a 407 (Proxy Authentication Required) response. The field value consists of a challenge that indicates the authentication scheme and parameters applicable to the proxy for this Request-URI.

Definition at line 90 of file nanohttp-response.h.

#define HEADER_RETRY_AFTER   "Retry-After"
 

The Retry-After response-header field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected to be unavailable to the requesting client. This field MAY also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked wait before issuing the redirected request. The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.

Definition at line 103 of file nanohttp-response.h.

#define HEADER_SERVER   "Server"
 

The Server response-header field contains information about the software used by the origin server to handle the request. The field can contain multiple product tokens (section 3.8) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance for identifying the application.

Definition at line 114 of file nanohttp-response.h.

#define HEADER_VARY   "Vary"
 

The Vary field value indicates the set of request-header fields that fully determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request without revalidation. For uncacheable or stale responses, the Vary field value advises the user agent about the criteria that were used to select the representation. A Vary field value of "*" implies that a cache cannot determine from the request headers of a subsequent request whether this response is the appropriate representation. See RFC 2616 section 13.6 for use of the Vary header field by caches.

See also:
http://www.ietf.org/rfc/rfc2616.txt

Definition at line 130 of file nanohttp-response.h.

#define HEADER_WWW_AUTHENTICATE   "WWW-Authenticate"
 

The WWW-Authenticate response-header field MUST be included in 401 (Unauthorized) response messages. The field value consists of at least one challenge that indicates the authentication scheme(s) and parameters applicable to the Request-URI.

WWW-Authenticate = "WWW-Authenticate" ":" 1challenge

The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" [43]. User agents are advised to take special care in parsing the WWW-Authenticate field value as it might contain more than one challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a comma-separated list of authentication parameters.

See also:
http://www.ietf.org/rfc/rfc2617.txt

Definition at line 151 of file nanohttp-response.h.

Referenced by httpd_send_unauthorized().


Generated on Thu Jan 25 23:36:04 2007 for csoap by  doxygen 1.4.6