HTTP Request HeaderRequest Header
accept Specifies the type of content that the client can receive. such as accept:text/plain, text/htmlaccept-charset the set of character encodings that the browser can accept. such as accept-charset: iso-8859-5accept-encoding specifies that the Web server that the browser can support returns the content compression encoding type. such as accept-encoding: compress, gzipaccept-language the language that the browser can accept. such as accept-language:en,zhaccept-ranges can request one or more child range fields for a page entity. such as accept-ranges: bytesauthorization http authorized Certificate of authorization. such as Authorization:basic qwxhzgrpbjpvcgvuihnlc2ftzq==cache-control Specifies the caching mechanism that requests and responses follow. such as cache-control:no-cacheconnection indicates whether a persistent connection is required. (http 1.1 default for persistent connections). such as connection:closecookie When a http request is sent, all cookie values stored under that request domain are sent to the Web server. such as cookies: $Version =1; skin=new; content-length The requested content length. such as content-length:348content-type MIME information corresponding to the entity requested. such as Content-type:application/x-www-form-urlencodeddate The date and time the request was sent. such as date:tue, 15 nov 2010 08:12:31 gmtexpect The specific server behavior of the request. such as expect:100-continuefrom email of the user who made the request. such as from:[email protected]host Specifies the domain name and port number of the requested server. such as host:www.zcmhi.comif-match only valid if the requested content matches the entity. such as If-match: "737060cd8c284d8af7ad3082f209582d" If-modified-since if the requested part is modified after the specified time, the request succeeds, and the 304 code is returned without modification. such as if-modified-since: sat, 29 oct 2010 19:43:31 gmtif-none-match If the content does not change return 304 code, The parameter is the server's previously sent ETag, and the server responds to the ETag to determine whether the change. such as if-none-match: "737060cd8c284d8af7ad3082f209582d" if-range if the entity does not change, The server sends the missing part of the client, otherwise it sends the entire entity. The parameters are also etag. such as if-range: "737060cd8c284d8af7ad3082f209582d" if-unmodified-since requests success only if the entity has not been modified since the specified time. such as if-unmodified-since: sat, 29 oct 2010 19:43:31 gmtmax-forwards Limit the time that information is transmitted through the agent and the gateway. such as MAX-FORWARDS:10PRAGMA     &Nbsp; is used to include implementation-specific instructions. such as pragma:no-cacheproxy-authorization The authorization certificate to connect to the agent. such as proxy-authorization:basic qwxhzgrpbjpvcgvuihnlc2ftzq==range Only part of the entity is requested, specifying the range. such as range:bytes=500-999referer the address of the previous page, which is immediately followed by the current request page, which is the route. such as referer:http://www.zcmhi.com/archives/71.htmlte The client is willing to accept the transfer encoding and notifies the server to accept the tail header information. such as TE: TRAILERS,DEFLATE;Q=0.5UPGRADE          &Nbsp; Specifies some kind of transport protocol to the server for the server to convert (if supported). such as upgrade: http/2.0, shttp/1.3, irc/6.9, rta/x11user-agent The content of the user-agent contains the user information that made the request. such as user-agent: mozilla/5.0 (linux; x11) via Notifies the intermediary gateway or proxy server address, communication protocol. such as via:1.0 fred, 1.1 nowhere.com (apache/1.1) warning Warning information about the message entity. such as Warn:199 miscellaneous warning
HTTP Responses HeaderResponse Header
accept-ranges Indicates whether the server supports the specified range request and what kind of segmentation request. such as accept-ranges: bytesage Estimated time (in seconds, non-negative) formed from the original server to the proxy cache. such as age: 12allow a valid request behavior for a network resource is not allowed to return 405. such as allow: get,headcache-control tells all caching mechanisms whether they can be cached and which type. such as cache-control: no-cachecontent-encoding The return content compression encoding type supported by the web server. such as content-encoding: gzipcontent-language the language of the response body. such as Content-language:en,zhcontent-length the length of the response body. such as content-length:348content-location request a resource that can be substituted for another address. such as content-location: /index.htmcontent-md5 returns the MD5 checksum value of the resource. such as content-md5:q2hly2sgsw50zwdyaxr5iq==content-range the byte position of this section in the entire returned body. such as content-range: bytes 21010-47021/47022content-type returns the MIME type of the content. such as content-type:text/html; charset=utf-8date RAW Server Message issueThe time. such as date:tue, 15 nov 2010 08:12:31 gmtetag The current value of the entity label of the request variable. such as etag: "737060cd8c284d8af7ad3082f209582d" expires date and time when the response expires. such as expires:thu, 01 dec 2010 16:00:00 gmtlast-modified last modified time to request resources. such as last-modified:tue, 15 nov 2010 12:45:26 gmtlocation Used to redirect the receiver to the location of the non-request URL to complete the request or identify the new resource. such as location: http://www.zcmhi.com/archives/94.htmlpragma includes implementing a specific instruction that can be applied to any receiver on the response chain. such as pragma: no-cacheproxy-authenticate It points out the authentication scheme and the parameters that can be applied to the proxy on that URL. such as proxy-authenticate: basicrefresh applied to redirection or a new resource was created, redirected after 5 seconds (proposed by Netscape, supported by most browsers). such as refresh: 5; url=http://www.zcmhi.com/archives/94.htmlretry-after notifies the client to try again after a specified time if the entity is temporarily undesirable. such as retry-after: 120server web Server Software name. such as server:apache/1.3.27 (Unix) (red-hat/linux) set-cookie set Http cookie. such as set-cookie:userid=johndoe; max-age=3600; version=1trailer Indicates that the header domain exists at the end of the chunked transfer encoding. such as trailer:max-forwardstransfer-encoding File transfer encoding. such as transfer-encoding:chunkedvary tells the downstream agent whether to use the cache response or request from the original server. such as vary: *via tells the proxy client where the response was sent. such as via:1.0 fred, 1.1 nowhere.com (apache/1.1) warning warns about possible problems with the entity. such as warning:199 miscellaneous warningwww-authenticate indicates the authorization scheme that the client request entity should use. such as Www-authenticate:basic
This article is from "Gan nan has" blog, please be sure to keep this source http://changfei.blog.51cto.com/4848258/1659630
HTTP request header and response header comments