Edit

Share via


HttpResponseHeader Enum

Definition

The HTTP headers that can be specified in a server response.

public enum class HttpResponseHeader
public enum HttpResponseHeader
type HttpResponseHeader = 
Public Enum HttpResponseHeader
Inheritance
HttpResponseHeader

Fields

Name Value Description
CacheControl 0

The Cache-Control header, which specifies caching directives that must be obeyed by all caching mechanisms along the request/response chain.

Connection 1

The Connection header, which specifies options that are desired for a particular connection.

Date 2

The Date header, which specifies the date and time at which the response originated.

KeepAlive 3

The Keep-Alive header, which specifies a parameter to be used to maintain a persistent connection.

Pragma 4

The Pragma header, which specifies implementation-specific directives that might apply to any agent along the request/response chain.

Trailer 5

The Trailer header, which specifies that the indicated header fields are present in the trailer of a message that is encoded with chunked transfer-coding.

TransferEncoding 6

The Transfer-Encoding header, which specifies what (if any) type of transformation has been applied to the message body.

Upgrade 7

The Upgrade header, which specifies additional communications protocols that the client supports.

Via 8

The Via header, which specifies intermediate protocols to be used by gateway and proxy agents.

Warning 9

The Warning header, which specifies additional information about that status or transformation of a message that might not be reflected in the message.

Allow 10

The Allow header, which specifies the set of HTTP methods that are supported.

ContentLength 11

The Content-Length header, which specifies the length, in bytes, of the accompanying body data.

ContentType 12

The Content-Type header, which specifies the MIME type of the accompanying body data.

ContentEncoding 13

The Content-Encoding header, which specifies the encodings that have been applied to the accompanying body data.

ContentLanguage 14

The Content-Language header, which specifies the natural language or languages of the accompanying body data.

ContentLocation 15

The Content-Location header, which specifies a URI from which the accompanying body can be obtained.

ContentMd5 16

The Content-MD5 header, which specifies the MD5 digest of the accompanying body data, for the purpose of providing an end-to-end message integrity check. Due to collision problems with MD5, Microsoft recommends a security model based on SHA256 or better.

ContentRange 17

The Range header, which specifies the subrange or subranges of the response that the client requests be returned in lieu of the entire response.

Expires 18

The Expires header, which specifies the date and time after which the accompanying body data should be considered stale.

LastModified 19

The Last-Modified header, which specifies the date and time at which the accompanying body data was last modified.

AcceptRanges 20

The Accept-Ranges header, which specifies the range that is accepted by the server.

Age 21

The Age header, which specifies the time, in seconds, since the response was generated by the originating server.

ETag 22

The Etag header, which specifies the current value for the requested variant.

Location 23

The Location header, which specifies a URI to which the client is redirected to obtain the requested resource.

ProxyAuthenticate 24

The Proxy-Authenticate header, which specifies that the client must authenticate itself to a proxy.

RetryAfter 25

The Retry-After header, which specifies a time (in seconds), or a date and time, after which the client can retry its request.

Server 26

The Server header, which specifies information about the originating server agent.

SetCookie 27

The Set-Cookie header, which specifies cookie data that is presented to the client.

Vary 28

The Vary header, which specifies the request headers that are used to determine whether a cached response is fresh.

WwwAuthenticate 29

The WWW-Authenticate header, which specifies that the client must authenticate itself to the server.

Remarks

The appropriate contents of various headers are described in detail in the HTTP/1.1 specification.

Applies to

See also