Overview#

HTTP Header Field are used to precisely describe the resource being fetched or the behavior of the server or the client.

HTTP Header Field are defined in a IANA Registry Message Headers

HTTP Header Field may be one of the following:

• HTTP Entity Header
• HTTP Request Header
• HTTP Response Header

The HTTP Method/HTTP Status Code line and HTTP Header Fields MUST all end with <CR><LF> (that is, a carriage return followed by a line feed). The empty line must consist of only <CR><LF> and no other whitespace.

Field Order#

The order in which HTTP Header Field with differing field names are received is not significant.

HTTP Header Directives#

Some HTTP Header Fields have HTTP Header Directives defined.

For example the "Cache-Control" HTTP Header Field is used to specify HTTP Cache Directives for caches along the request/response chain.

More Information#

There might be more information for this subject on one of the following:

• Accept header
• Accept-Language
• Authorization Header
• Basic Authentication Scheme
• CSRF Token
• Cache-Control
• Content-Encoding
• Content-Language
• Content-Length
• Content-Type
• Covert Redirect Vulnerability
• Cross Origin Resource Sharing
• Cross-site request forgery
• DNT
• Etag
• Fetch API
• HTTP 204
• HTTP 302
• HTTP 304
• HTTP 503
• HTTP Body
• HTTP Cache Directive
• HTTP Conditional Request
• HTTP Entity Header
• HTTP HEAD
• HTTP Header Directive
• HTTP Header Field
• HTTP Request Header
• HTTP Response Header
• HTTP Strict Transport Security
• HTTP Warn Codes
• Hypertext Transfer Protocol (HTTP 1.1) Conditional Requests
• Lag HTTP headers
• Language-Tag
• OAuth 2.0 Bearer Token Usage
• Openid-configuration
• PeopleSoft Integrations
• Public Key Pinning Extension for HTTP
• SCIM Create Request
• Sec-Token-Binding
• Strict-Transport-Security
• Token Binding over HTTP
• WWW-Authenticate
• Warning
• Web Linking