HTTP Request Header
Header Interpretation Example:
Accept Specify the type of content the client can receive Accept: text/plain, text/html
Accept-Charset The character coding set acceptable to the browser. Accept-Charset: iso-8859-5
Accept-Encoding Specifies the type of content compression code that the browser can support. Accept-Encoding: compress, gzip
Accept-Language Languages acceptable to browser Accept-Language: en,zh
Accept-Ranges You can request one or more sub-range fields of a web entity Accept-Ranges: bytes
Authorization HTTP Authorized Certificate Organisation
Cache-Control Designation of a cache mechanism for requests and responses to compliance Cache-Control: no-cache
Connection indicates whether a permanent connection is required. (HTTP 1.1 default lasting connection) Connection: close
Cookie When HTTP requests to be sent, all cookies stored under the requested domain are sent together to the web server. Cookie: $Version=1; Skin=new;
Content-Length Length of content requested Content-Length: 348
Content-Type MIME information requested in relation to entities Content-Type: application/x-www-form-urlencoded
Date Date and time of request Date: Tue, 15 Nov 2010 08:12:31 GMT
Expect Specific server behaviour requested Expect: 100-continue
From Email for requesting users From: user@jsons.cn
Host Specify the domain name and port number of the requested server Host: www.jsons.cn
If-Match Only if the request matches the entity If-Match: "Specific value"
If-Modified-Since If the part of the request is modified after the specified time, the request is successful and the code 304 is returned if not modified If-Modified-Since: Sat, 29 Oct 2010 19:43:31 GMT
If-None-Match If content does not change returns the 304 code, the parameter is the Etag previously sent by the server and the change is judged against the Etag responding server If-None-Match: "Specific value"
If-Range If the entity does not change, the server sends the lost part of the client, or sends the entire entity. The parameter is also Etag If-Range: "Specific value"
If-Unmodified-Since Successful request only if the entity has not been modified after the specified time If-Unmodified-Since: Sat, 29 Oct 2010 19:43:31 GMT
Max-Forwards Limit the time for information to be transmitted through agents and gateways Max-Forwards: 10
Pragma Use to include specific instructions Pragma: no-cache
Proxy-Authorization Can not open message Proxy-Authorization: Link to proxy authentication
Range Only part of the entity requested, scope specified Range: bytes=500-999
Referer The address of the previous page, the current request page immediately follows, and is on the way Referer: http://www.jsons.cn
TE Client willing to accept transfer code and notify the server to accept end-up information TE: trailers,deflate;q=0.5
Upgrade Specify some transmission protocol to the server for server conversion (if supported) Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
User-Agent User-Agent contains the user message to send the request User-Agent: Mozilla/5.0 (Linux; X11)
Via Notification of intermediate gateway or proxy address, communication protocol Via: 1.0 fred, 1.1 nowhere.com (Apache/1.1)
Warning Warning information about the message entity Warn: 199 Miscellaneous warning
HTTP Responses Header
Header Interpretation Example:
Accept-Ranges Indicate if the server supports the scope of the assignment and what type of segment request Accept-Ranges: bytes
Age Estimated time from original server to proxy cache formation (in seconds, non-negative) Age: 12
Allow Effective request for a network resource is not allowed to return 405 Allow: GET, HEAD
Cache-Control Tell all the cache mechanisms if they can cache and what type. Cache-Control: no-cache
Content-Encoding The return content compression encoding type supported by the web server. Content-Encoding: gzip
Content-Language Language of the respondent Content-Language: en,zh
Content-Length Length of Response Content-Length: 348
Content-Location Alternative address for which resources are requested Content-Location: /index.htm
Content-MD5 Returns resource MD5 validation Content-MD5: MD5 Validation
Content-Range Returns the byte position of this part of the body Content-Range: bytes 21010-47021/47022
Content-Type Returns mimetype of content Content-Type: text/html; charset=utf-8
Date Original server message dispatch time Date: Tue, 15 Nov 2010 08:12:31 GMT
ETag Current value of the entity label of the requested variable ETag: "Request variable entity label current value"
Expires Date and time of response to expiry Expires: Thu, 01 Dec 2010 16:00:00 GMT
Last-Modified Final revision of resource requests Last-Modified: Tue, 15 Nov 2010 12:45:26 GMT
Location Redirect recipients to non-request URLs to complete requests or to mark new resources Location: http://www.jsons.cn
Pragma Including achieving specific instructions, which can be applied to any recipient in the response chain Pragma: no-cache
Proxy-Authenticate It points to the parameters of the authentication program and the URL that can be applied to the agent Proxy-Authenticate: Basic
refresh Used to reorient or create a new resource, redirected after 5 seconds (proposed by web view, supported by most browsers)
Refresh: 5; url= http://www.jsons.cn
Retry-After If the entity is temporarily undesirable, notify the client to try again after the specified time Retry-After: 120
Server Web Server Software Name Server: Apache/1.3.27 (Unix) (Red-Hat/Linux)
Set-Cookie Setup Http Cookie Set-Cookie: UserID=JohnDoe; Max-Age=3600; Version=1
Trailer Note the head field exists at the end of the branch transfer code Trailer: Max-Forwards
Transfer-Encoding File transfer code Transfer-Encoding:chunked
Vary Tell downstream agents whether to use a cache response or request from the original server Vary: *
Via Tell the client where the response was sent. Via: 1.0 fred, 1.1 nowhere.com (Apache/1.1)
Warning Warning entities of possible problems Warning: 199 Miscellaneous warning
WWW-Authenticate Demonstrate the delegation of authority that the client requesting entity should use WWW-Authenticate: Basic

HTTP responders online. HTTP requests a full head.

HTTP request header provides information on the requesting, responding or other transmitting entity, and HTTP header information includes generic header, requesting header, response header and the first four parts of the entity

Each domain consists of a domain name, colon (:) and three dimensions of domain value

Common header: available for request and response, as a whole rather than as a specific resource-related issue

Request header: allows clients to transmit information about themselves and the desired form of response

Response header: server and response to transmission of information

Entity header: definition of the information that is transferred to the resource, i.e. that can be used for the request and that can also be used to respond to the request

Recent tools: