HttpRequestHeader Enum
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
The HTTP headers that may be specified in a client request.
public enum class HttpRequestHeader
public enum HttpRequestHeader
type HttpRequestHeader =
Public Enum HttpRequestHeader
- Inheritance
Fields
Accept | 20 | The Accept header, which specifies the MIME types that are acceptable for the response. |
AcceptCharset | 21 | The Accept-Charset header, which specifies the character sets that are acceptable for the response. |
AcceptEncoding | 22 | The Accept-Encoding header, which specifies the content encodings that are acceptable for the response. |
AcceptLanguage | 23 | The Accept-Language header, which specifies that natural languages that are preferred for the response. |
Allow | 10 | The Allow header, which specifies the set of HTTP methods supported. |
Authorization | 24 | The Authorization header, which specifies the credentials that the client presents in order to authenticate itself to the server. |
CacheControl | 0 | The Cache-Control header, which specifies directives that must be obeyed by all cache control mechanisms along the request/response chain. |
Connection | 1 | The Connection header, which specifies options that are desired for a particular connection. |
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(s) of the accompanying body data. |
ContentLength | 11 | The Content-Length header, which specifies the length, in bytes, of the accompanying body data. |
ContentLocation | 15 | The Content-Location header, which specifies a URI from which the accompanying body may 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 Content-Range header, which specifies where in the full body the accompanying partial body data should be applied. |
ContentType | 12 | The Content-Type header, which specifies the MIME type of the accompanying body data. |
Cookie | 25 | The Cookie header, which specifies cookie data presented to the server. |
Date | 2 | The Date header, which specifies the date and time at which the request originated. |
Expect | 26 | The Expect header, which specifies particular server behaviors that are required by the client. |
Expires | 18 | The Expires header, which specifies the date and time after which the accompanying body data should be considered stale. |
From | 27 | The From header, which specifies an Internet Email address for the human user who controls the requesting user agent. |
Host | 28 | The Host header, which specifies the host name and port number of the resource being requested. |
IfMatch | 29 | The If-Match header, which specifies that the requested operation should be performed only if the client's cached copy of the indicated resource is current. |
IfModifiedSince | 30 | The If-Modified-Since header, which specifies that the requested operation should be performed only if the requested resource has been modified since the indicated date and time. |
IfNoneMatch | 31 | The If-None-Match header, which specifies that the requested operation should be performed only if none of client's cached copies of the indicated resources are current. |
IfRange | 32 | The If-Range header, which specifies that only the specified range of the requested resource should be sent, if the client's cached copy is current. |
IfUnmodifiedSince | 33 | The If-Unmodified-Since header, which specifies that the requested operation should be performed only if the requested resource has not been modified since the indicated date and time. |
KeepAlive | 3 | The Keep-Alive header, which specifies a parameter used into order to maintain a persistent connection. |
LastModified | 19 | The Last-Modified header, which specifies the date and time at which the accompanying body data was last modified. |
MaxForwards | 34 | The Max-Forwards header, which specifies an integer indicating the remaining number of times that this request may be forwarded. |
Pragma | 4 | The Pragma header, which specifies implementation-specific directives that might apply to any agent along the request/response chain. |
ProxyAuthorization | 35 | The Proxy-Authorization header, which specifies the credentials that the client presents in order to authenticate itself to a proxy. |
Range | 37 | The Range header, which specifies the sub-range(s) of the response that the client requests be returned in lieu of the entire response. |
Referer | 36 | The Referer header, which specifies the URI of the resource from which the request URI was obtained. |
Te | 38 | The TE header, which specifies the transfer encodings that are acceptable for the response. |
Trailer | 5 | The Trailer header, which specifies the header fields present in the trailer of a message encoded with chunked transfer-coding. |
TransferEncoding | 6 | The Transfer-Encoding header, which specifies what (if any) type of transformation that has been applied to the message body. |
Translate | 39 | The Translate header, a Microsoft extension to the HTTP specification used in conjunction with WebDAV functionality. |
Upgrade | 7 | The Upgrade header, which specifies additional communications protocols that the client supports. |
UserAgent | 40 | The User-Agent header, which specifies information about the client agent. |
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. |
Remarks
The appropriate contents of various headers are described in detail in the HTTP/1.1 specification, available at rfc2616.