Front page > HTTP response header, HTTP request header

HTTP Request Header Request header

Name: HTTP response header, HTTP request header
Author: 录屏网

The HTTP request header comparison table provides you with HTTP request headers. HTTP response headers must be considered when writing collectors, API interfaces, simulated login http headers, remote acquisition of content, etc. HTTP Request Header, HTTP Responses Header, HTTP docking Header Complete request header information

Header	Explain	Example
Accept	Specify the content types the client can receive	Accept: text/plain, text/html
Accept-Charset	The character encoding set that the browser can accept.	Accept-Charset: iso-8859-5
Accept-Encoding	Specifies the compression encoding type of content returned by the web server that the browser can support.	Accept-Encoding: compress, gzip
Accept-Language	Languages accepted by the browser	Accept-Language: en,zh
Accept-Ranges	You can request one or more sub-range fields of the web page entity	Accept-Ranges: bytes
Authorization	Authorization certificate for HTTP authorization	Authorization: Certificate of Authorization
Cache-Control	Specify the caching mechanism that requests and responses follow	Cache-Control: no-cache
Connection	Indicates whether a persistent connection is required. (HTTP 1.1 makes persistent connections by default)	Connection: close
Cookie	When an HTTP request is sent, all cookie values stored in the requested domain name will be sent to the web server.	Cookie: $Version=1; Skin=new;
Content-Length	Requested content length	Content-Length: 348
Content-Type	The requested MIME information corresponding to the entity	Content-Type: application/x-www-form-urlencoded
Date	The date and time the request was sent	Date: Tue, 15 Nov 2010 08:12:31 GMT
Expect	Request specific server behavior	Expect: 100-continue
From	Email of the user who made the request	From: [email protected]
Host	Specify the domain name and port number of the requested server	Host: www.jsons.cn
If-Match	Valid only if the request content matches the entity	If-Match: “Specific value”
If-Modified-Since	If the requested part is modified after the specified time, the request is successful. If it is not modified, a 304 code is returned.	If-Modified-Since: Sat, 29 Oct 2010 19:43:31 GMT
If-None-Match	If the content has not changed, a 304 code is returned. The parameter is the Etag previously sent by the server. Compare it with the Etag responded by the server to determine whether it has changed.	If-None-Match: Specific value
If-Range	If the entity has not changed, the server sends the client the missing portion, otherwise the entire entity is sent. The parameter is also Etag	If-Range: Specific value
If-Unmodified-Since	The request succeeds 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 that information travels through proxies and gateways	Max-Forwards: 10
Pragma	Used to contain implementation-specific instructions	Pragma: no-cache
Proxy-Authorization	Authorization certificate to connect to the agent	Proxy-Authorization: 链接到代理的授权证书
Range	Request only part of the entity, specify the range	Range: bytes=500-999
Referer	The address of the previous web page, followed by the current requested web page, that is, the origin	Referer: http://www.jsons.cn
TE	The client is willing to accept the transfer encoding and notifies the server to accept the tail plus header information.	TE: trailers,deflate;q=0.5
Upgrade	Specifies a transport protocol for the server to convert (if supported)	Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
User-Agent	The content of User-Agent contains information about the user who made the request	User-Agent: Mozilla/5.0 (Linux; X11)
Via	Notify intermediate gateway or proxy server address, communication protocol	Via: 1.0 fred, 1.1 nowhere.com (Apache/1.1)
Warning	Warning information about message entities	Warn: 199 Miscellaneous warning