Online HTTP Header Collection

HTTP Request Header
Header Explanation Example
Accept Specifies the content types that the client can accept Accept: text/plain, text/html
Accept-Charset Character sets that the browser can accept Accept-Charset: iso-8859-5
Accept-Encoding Specifies the compression methods supported by the browser for web server responses. Accept-Encoding: compress, gzip
Accept-Language Languages accepted by the browser. Accept-Language: en,zh
Accept-Ranges One or more sub-range fields that can request entity ranges of a web page. Accept-Ranges: bytes
Authorization Authorization credentials for HTTP authorization. Authorization: Authorization credentials
Cache-Control Specifies the caching mechanism that both request and response must follow. Cache-Control: no-cache
Connection Indicates whether a persistent connection is required. (HTTP 1.1 defaults to persistent connection) Connection: close
Cookie When an HTTP request is sent, all cookie values stored under the request domain are sent to the web server. Cookie: $Version=1; Skin=new;
Content-Length Length of the request content. Content-Length: 348
Content-Type MIME information corresponding to the entity in the request. Content-Type: application/x-www-form-urlencoded
Date Date and time when the request was sent. Date: Tue, 15 Nov 2020 08:12:31 GMT
Expect Specific server behavior requested by the client. Expect: 100-continue
From Email address of the user making the request. From: [email protected]
Host Specifies the domain name and port number of the server to which the request is being sent. Host: www.1024xk.com
If-Match Only makes the request method effective if the contents match the entity. If-Match: "specific value"
If-Modified-Since If the requested part has been modified after the specified time, the request succeeds; otherwise, returns a 304 code. If-Modified-Since: Sat, 29 Oct 2010 19:43:31 GMT
If-None-Match Returns a 304 code if the content has not changed. Compares the Etag sent previously by the server with the Etag in the server's response to determine changes. If-None-Match: "specific value"
If-Range If the entity has not changed, the server sends the client the missing part; otherwise, it sends the entire entity. The parameter is also an Etag. If-Range: "specific value"
If-Unmodified-Since Only requests succeed if the entity has not been modified after the specified time. If-Unmodified-Since: Sat, 29 Oct 2010 19:43:31 GMT
Max-Forwards Limits the time information can be forwarded through proxies and gateways. Max-Forwards: 10
Pragma Used to include implementation-specific directives. Pragma: no-cache
Proxy-Authorization Authorization credentials for connecting to a proxy. Proxy-Authorization: credentials for connecting to a proxy
Range Requests only a part of the entity, specified by the range. Range: bytes=500-999
Referer Refers to the address of the previous web page from which the current request is made (i.e., the referrer). Referer: http://www.1024xk.com
TE Specifies the transfer encodings that the client is willing to accept and notifies the server of the transfer encodings it is willing to accept for response tailoring. TE: trailers,deflate;q=0.5
Upgrade Requests that the server switch protocols (if supported) to one specified in the Upgrade header. Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
User-Agent Contains information about the user agent that sent the request. User-Agent: Mozilla/5.0 (Linux; X11)
Via Informs the server of the intermediaries through which the request was sent, including communication protocols and addresses. Via: 1.0 fred, 1.1 nowhere.com (Apache/1.1)
Warning Provides additional information about the status or transformation of a message. Warn: 199 Miscellaneous warning
HTTP Responses Header
Header Explanation Example
Accept-Ranges Indicates whether the server supports range requests and which types of range requests are supported. Accept-Ranges: bytes
Age The age of the response since it was generated or validated at the origin server (in seconds, non-negative). Age: 12
Allow Specifies the methods allowed for a resource, otherwise returns a 405 Method Not Allowed. Allow: GET, HEAD
Cache-Control Specifies directives for caching mechanisms in both requests and responses. Cache-Control: no-cache
Content-Encoding Specifies the encoding formats the server supports for the response body. Content-Encoding: gzip
Content-Language Specifies the natural languages of the intended audience for the response body. Content-Language: en,zh
Content-Length The length of the response body in octets (8-bit bytes). Content-Length: 348
Content-Location An alternate location for the returned resource. Content-Location: /index.htm
Content-MD5 The MD5 digest of the entity-body for the purpose of providing an end-to-end message integrity check. Content-MD5: MD5 checksum
Content-Range Indicates the byte range within the full entity-body sent in the message. Content-Range: bytes 21010-47021/47022
Content-Type The media type of the body of the request or response. Content-Type: text/html; charset=utf-8
Date The date and time at which the message was originated at the server. Date: Tue, 15 Nov 2010 08:12:31 GMT
ETag An identifier for a specific version of a resource, often a hash of the resource. ETag: "entity-tag-value"
Expires The date and time after which the response is considered stale. Expires: Thu, 01 Dec 2010 16:00:00 GMT
Last-Modified The last modification date of the resource being returned. Last-Modified: Tue, 15 Nov 2010 12:45:26 GMT
Location Used in redirection, or when a new resource has been created. It indicates the URL to redirect the recipient to. Location: https://www.1024xk.com
Pragma Includes implementation-specific directives that might apply to any recipient along the request/response chain. Pragma: no-cache
Proxy-Authenticate Authenticates the user to a proxy server, indicating the authentication scheme and parameters applicable to the proxy for the requested URL. Proxy-Authenticate: Basic
refresh Specifies a time in seconds for the browser to wait before refreshing or redirecting the page.
Refresh: 5; url= https://www.1024xk.com
Retry-After If the entity is temporarily unavailable, it informs the client when to retry the request. Retry-After: 120
Server The name of the web server software. Server: Apache/1.3.27 (Unix) (Red-Hat/Linux)
Set-Cookie Sets an HTTP cookie. Set-Cookie: UserID=JohnDoe; Max-Age=3600; Version=1
Trailer Indicates that the indicated header field is present in the trailer of a chunked transfer encoding. Trailer: Max-Forwards
Transfer-Encoding Specifies the form of encoding used to safely transfer the entity to the user. Transfer-Encoding: chunked
Vary Informs downstream proxies how to match future request headers to decide whether to serve the requested resource from the cache or request it from the origin server. Vary: *
Via Informs the client of proxies through which the response was sent. Via: 1.0 fred, 1.1 nowhere.com (Apache/1.1)
Warning Warns of possible issues with the entity body. Warning: 199 Miscellaneous warning
WWW-Authenticate Indicates which authentication schemes should be used to access the requested entity. WWW-Authenticate: Basic

Introduction to Online HTTP Headers Tool

Our Online HTTP Headers Tool provides comprehensive information about HTTP headers used in requests and responses. HTTP headers are vital for conveying metadata between clients and servers, facilitating efficient communication over the web.

Using our Online HTTP Headers Tool is straightforward:

  • HTTP Headers Overview: Understand the purpose and usage of common HTTP headers in both requests and responses.
  • Request Headers: Learn about headers that allow clients to send information about themselves and their desired response format.
  • Response Headers: Explore headers used by servers to convey information about themselves and the transmitted data.
  • Entity Headers: Define headers that provide information about the resource being sent or requested.

Key features of our Online HTTP Headers Tool include:

  • Comprehensive Coverage: Detailed information on common HTTP headers for requests and responses.
  • Educational Resource: Suitable for learning HTTP header usage and best practices.
  • SEO Friendly: Provides structured information beneficial for web developers and SEO optimization.

Whether you're troubleshooting HTTP header issues, optimizing web performance, or enhancing SEO strategies, our Online HTTP Headers Tool offers valuable insights and resources.

Visit History:

Links: google