硬汉嵌入式论坛

 找回密码
 立即注册
查看: 2982|回复: 1
收起左侧

[Web前端] HTTP请求消息头域和响应消息头域

[复制链接]

1万

主题

6万

回帖

10万

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
107221
QQ
发表于 2017-8-7 01:12:41 | 显示全部楼层 |阅读模式
wiki中文:链接
wiki英文:链接
========================================
请求字段
协议头字段名说明示例状态
Accept能够接受的回应内容类型(Content-Types)。参见内容协商。Accept: text/plain常设
Accept-Charset能够接受的字符集Accept-Charset: utf-8常设
Accept-Encoding能够接受的编码方式列表。参考HTTP压缩Accept-Encoding: gzip, deflate常设
Accept-Language能够接受的回应内容的自然语言列表。参考 内容协商 。Accept-Language: en-US常设
Accept-Datetime能够接受的按照时间来表示的版本Accept-Datetime: Thu, 31 May 2007 20:35:00 GMT临时
Authorization用于超文本传输协议的认证的认证信息Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==常设
Cache-Control用来指定在这次的请求/响应链中的所有缓存机制 都必须 遵守的指令Cache-Control: no-cache常设
Connection该浏览器想要优先使用的连接类型
[sup][8][/sup]
Connection: keep-alive
Connection: Upgrade
常设
Cookie之前由服务器通过 Set- Cookie (下文详述)发送的一个 超文本传输协议CookieCookie: $Version=1; Skin=new;常设: 标准
Content-Length以 八位字节数组 (8位的字节)表示的请求体的长度Content-Length: 348常设
Content-MD5请求体的内容的二进制 MD5 散列值,以 Base64 编码的结果Content-MD5: Q2hlY2sgSW50ZWdyaXR5IQ==过时的[sup][9][/sup]
Content-Type请求体的 多媒体类型 (用于POST和PUT请求中)Content-Type: application/x-www-form-urlencoded常设
Date发送该消息的日期和时间(按照 RFC 7231 中定义的"超文本传输协议日期"格式来发送)Date: Tue, 15 Nov 1994 08:12:31 GMT常设
Expect表明客户端要求服务器做出特定的行为Expect: 100-continue常设
From发起此请求的用户的邮件地址From: user@example.com常设
Host服务器的域名(用于虚拟主机 ),以及服务器所监听的传输控制协议端口号。如果所请求的端口是对应的服务的标准端口,则端口号可被省略。
[sup][10][/sup] 自超文件传输协议版本1.1(HTTP/1.1)开始便是必需字段。
Host: en.wikipedia.org:80
Host: en.wikipedia.org
常设
If-Match仅当客户端提供的实体与服务器上对应的实体相匹配时,才进行对应的操作。主要作用时,用作像 PUT 这样的方法中,仅当从用户上次更新某个资源以来,该资源未被修改的情况下,才更新该资源。If-Match: "737060cd8c284d8af7ad3082f209582d"常设
If-Modified-Since允许在对应的内容未被修改的情况下返回304未修改( 304 Not Modified )If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT常设
If-None-Match允许在对应的内容未被修改的情况下返回304未修改( 304 Not Modified ),参考 超文本传输协议 的实体标记If-None-Match: "737060cd8c284d8af7ad3082f209582d"常设
If-Range如果该实体未被修改过,则向我发送我所缺少的那一个或多个部分;否则,发送整个新的实体If-Range: "737060cd8c284d8af7ad3082f209582d"常设
If-Unmodified-Since仅当该实体自某个特定时间已来未被修改的情况下,才发送回应。If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT常设
Max-Forwards限制该消息可被代理及网关转发的次数。Max-Forwards: 10常设
Origin发起一个针对 跨来源资源共享 的请求(要求服务器在回应中加入一个‘访问控制-允许来源’('Access-Control-Allow-Origin')字段)。Origin: http://www.example-social-network.com常设: 标准
Pragma与具体的实现相关,这些字段可能在请求/回应链中的任何时候产生多种效果。Pragma: no-cache常设但不常用
Proxy-Authorization用来向代理进行认证的认证信息。Proxy-Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==常设
Range仅请求某个实体的一部分。字节偏移以0开始。参见字节服务Range: bytes=500-999常设
Referer [sic] [sup][11][/sup]表示浏览器所访问的前一个页面,正是那个页面上的某个链接将浏览器带到了当前所请求的这个页面。Referer: http://en.wikipedia.org/wiki/Main_Page常设
TE浏览器预期接受的传输编码方式:可使用回应协议头 Transfer-Encoding 字段中的值;另外还可用"trailers"(与"分块 "传输方式相关)这个值来表明浏览器希望在最后一个尺寸为0的块之后还接收到一些额外的字段。TE: trailers, deflate常设
User-Agent浏览器的浏览器身份标识字符串User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/21.0常设
Upgrade要求服务器升级到另一个协议。Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11常设
Via向服务器告知,这个请求是由哪些代理发出的。Via: 1.0 fred, 1.1 example.com (Apache/1.1)常设
Warning一个一般性的警告,告知,在实体内容体中可能存在错误。Warning: 199 Miscellaneous warning常设

常见的非标准请求字段
字段名说明示例
X-Requested-With主要用于标识 Ajax 及可扩展标记语言 请求。大部分的JavaScript框架会发送这个字段,且将其值设置为 XMLHttpRequestX-Requested-With: XMLHttpRequest
DNT[sup][12][/sup]请求某个网页应用程序停止跟踪某个用户。在火狐浏览器中,相当于X-Do-Not-Track协议头字段(自 Firefox/4.0 Beta 11 版开始支持)。SafariInternet Explorer 9 也支持这个字段。2011年3月7日,草案提交IETF。[sup][13][/sup] 万维网协会 的跟踪保护工作组正在就此制作一项规范。[sup][14][/sup]DNT: 1 (DNT启用)
DNT: 0 (DNT被禁用)
X-Forwarded-For[sup][15][/sup]一个事实标准 ,用于标识某个通过超文本传输协议代理或负载均衡连接到某个网页服务器的客户端的原始互联网地址X-Forwarded-For: client1, proxy1, proxy2
X-Forwarded-For: 129.78.138.66, 129.78.64.103
X-Forwarded-Host[sup][16][/sup]一个事实标准 ,用于识别客户端原本发出的 Host 请求头部[sup][17][/sup]。X-Forwarded-Host: en.wikipedia.org:80
X-Forwarded-Host: en.wikipedia.org
X-Forwarded-Proto[sup][18][/sup]一个事实标准,用于标识某个超文本传输协议请求最初所使用的协议。[sup][19][/sup]X-Forwarded-Proto: https
Front-End-Https[sup][20][/sup]被微软的服务器和负载均衡器所使用的非标准头部字段。Front-End-Https: on
X-Http-Method-Override[sup][21][/sup]请求某个网页应用程序使用该协议头字段中指定的方法(一般是PUT或DELETE)来覆盖掉在请求中所指定的方法(一般是POST)。当某个浏览器或防火墙阻止直接发送PUT 或DELETE 方法时(注意,这可能是因为软件中的某个漏洞,因而需要修复,也可能是因为某个配置选项就是如此要求的,因而不应当设法绕过),可使用这种方式。X-HTTP-Method-Override: DELETE
X-ATT-DeviceId[sup][22][/sup]使服务器更容易解读AT&T设备User-Agent字段中常见的设备型号、固件信息。X-Att-Deviceid: GT-P7320/P7320XXLPG
X-Wap-Profile[sup][23][/sup]链接到互联网上的一个XML文件,其完整、仔细地描述了正在连接的设备。右侧以为AT&T Samsung Galaxy S2提供的XML文件为例。x-wap-profile:http://wap.samsungmobile.com/uaprof/SGH-I777.xml
Proxy-Connection[sup][24][/sup]该字段源于早期超文本传输协议版本实现中的错误。与标准的连接(Connection)字段的功能完全相同。Proxy-Connection: keep-alive
X-Csrf-Token[sup][25][/sup]用于防止 跨站请求伪造。 辅助用的头部有 X-CSRFToken[sup][26][/sup] 或 X-XSRF-TOKEN[sup][27][/sup]X-Csrf-Token: i8XNjC4b8KVok4uw5RftR38Wgp2BFwql

回应字段
Field nameDescriptionExampleStatus
Access-Control-Allow-Origin指定哪些网站可参与到跨来源资源共享过程中Access-Control-Allow-Origin: *临时
Accept-Patch[sup][28][/sup]指定服务器支持的文件格式类型。Accept-Patch: text/example;charset=utf-8常设
Accept-Ranges这个服务器支持哪些种类的部分内容范围Accept-Ranges: bytes常设
Age这个对象在代理缓存中存在的时间,以秒为单位Age: 12常设
Allow对于特定资源有效的动作。针对HTTP/405这一错误代码而使用Allow: GET, HEAD常设
Cache-Control向从服务器直到客户端在内的所有缓存机制告知,它们是否可以缓存这个对象。其单位为秒Cache-Control: max-age=3600常设
Connection针对该连接所预期的选项
[sup][8][/sup]
Connection: close常设
Content-Disposition[sup][29][/sup]一个可以让客户端下载文件并建议文件名的头部。文件名需要用双引号包裹。Content-Disposition: attachment; filename="fname.ext"常设
Content-Encoding在数据上使用的编码类型。参考 超文本传输协议压缩 。Content-Encoding: gzip常设
Content-Language内容所使用的语言
[sup][30][/sup]
Content-Language: da常设
Content-Length回应消息体的长度,以 字节 (8位为一字节)为单位Content-Length: 348常设
Content-Location所返回的数据的一个候选位置Content-Location: /index.htm常设
Content-MD5回应内容的二进制 MD5 散列,以 Base64 方式编码Content-MD5: Q2hlY2sgSW50ZWdyaXR5IQ==过时的[sup][31][/sup]
Content-Range这条部分消息是属于某条完整消息的哪个部分Content-Range: bytes 21010-47021/47022常设
Content-Type当前内容的MIME类型Content-Type: text/html; charset=utf-8常设
Date此条消息被发送时的日期和时间(按照 RFC 7231 中定义的“超文本传输协议日期”格式来表示)Date: Tue, 15 Nov 1994 08:12:31 GMT常设
ETag对于某个资源的某个特定版本的一个标识符,通常是一个 消息散列ETag: "737060cd8c284d8af7ad3082f209582d"常设
Expires指定一个日期/时间,超过该时间则认为此回应已经过期Expires: Thu, 01 Dec 1994 16:00:00 GMT常设: 标准
Last-Modified所请求的对象的最后修改日期(按照 RFC 7231 中定义的“超文本传输协议日期”格式来表示)Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT常设
Link用来表达与另一个资源之间的类型关系,此处所说的类型关系是在 RFC 5988 中定义的Link: </feed>; rel="alternate"[sup][32][/sup]常设
Location用来 进行重定向,或者在创建了某个新资源时使用。Location: http://www.w3.org/pub/WWW/People.html常设
P3PThis field is supposed to set P3P policy, in the form of P3P:CP="your_compact_policy". However, P3P did not take off,[sup][33][/sup]most browsers have never fully implemented it, a lot of websites set this field with fake policy text, that was enough to fool browsers the existence of P3P policy and grant permissions for third party cookies.P3P: CP="This is not a P3P policy! See http://www.google.com/support/ac ... p;amp;answer=151657 for more info."常设
Pragma与具体的实现相关,这些字段可能在请求/回应链中的任何时候产生多种效果。Pragma: no-cache常设
Proxy-Authenticate要求在访问代理时提供身份认证信息。Proxy-Authenticate: Basic常设
Public-Key-Pins[sup][34][/sup]用于缓解中间人攻击,声明网站认证使用的传输层安全协议证书的散列值Public-Key-Pins: max-age=2592000; pin-sha256="E9CZ9INDbd+2eRQozYqqbQ2yXLVKB9+xcprMF+44U1g=";常设
RefreshUsed in redirection, or when a new resource has been created. This refresh redirects after 5 seconds.Refresh: 5; url=http://www.w3.org/pub/WWW/People.htmlProprietary and non-标准: a header extension introduced by Netscape and supported by most web browsers.
Retry-After如果某个实体临时不可用,则,此协议头用来告知客户端日后重试。其值可以是一个特定的时间段(以秒为单位)或一个超文本传输协议日期。 [sup][35][/sup]
    [li]Example 1: Retry-After: 120[/li][li]Example 2: Retry-After: Fri, 07 Nov 2014 23:59:59 GMT[/li]

常设
Server服务器的名字Server: Apache/2.4.1 (Unix)常设
Set-CookieHTTP cookieSet-Cookie: UserID=JohnDoe; Max-Age=3600; Version=1常设: 标准
Status通用网关接口 协议头字段,用来说明当前这个超文本传输协议回应的 状态 。普通的超文本传输协议回应,会使用单独的“状态行”("Status-Line")作为替代,这一点是在 RFC 7230 中定义的。

[sup][36][/sup]
Status: 200 OKNot listed as a registered field name
Strict-Transport-SecurityHTTP 严格传输安全这一头部告知客户端缓存这一强制 HTTPS 策略的时间,以及这一策略是否适用于其子域名。Strict-Transport-Security: max-age=16070400; includeSubDomains常设: 标准
Trailer这个头部数值指示了在这一系列头部信息由由分块传输编码编码。Trailer: Max-Forwards常设
Transfer-Encoding用来将实体安全地传输给用户的编码形式。当前定义的方法包括:分块(chunked)、compress、deflate、gzip和identity。Transfer-Encoding: chunked常设
Upgrade要求客户端升级到另一个协议。Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11常设
Vary告知下游的代理服务器,应当如何对未来的请求协议头进行匹配,以决定是否可使用已缓存的回应内容而不是重新从原始服务器请求新的内容。Vary: *常设
Via告知代理服务器的客户端,当前回应是通过什么途径发送的。Via: 1.0 fred, 1.1 example.com (Apache/1.1)常设
Warning一般性的警告,告知在实体内容体中可能存在错误。Warning: 199 Miscellaneous warning常设
WWW-Authenticate表明在请求获取这个实体时应当使用的认证模式。WWW-Authenticate: Basic常设
X-Frame-Options[sup][37][/sup]Clickjacking protection: deny - no rendering within a frame, sameorigin - no rendering if origin mismatch, allow-from - allow from specified location, allowall - non-标准, allow from any locationX-Frame-Options: deny过时的[sup][38][/sup]

常见的非标准回应字段
字段名说明示例
X-XSS-Protection[sup][39][/sup]跨站脚本攻击 (XSS)过滤器X-XSS-Protection: 1; mode=block
Content-Security-Policy, X-Content-Security-Policy, X-WebKit-CSP[sup][40][/sup]内容安全策略定义。X-WebKit-CSP: default-src 'self'
X-Content-Type-Options[sup][41][/sup]唯一允许的数值为"nosniff", 防止 Internet Explorer 对文件进行MIME类型嗅探。这也对 Google Chrome 下载扩展时适用。[sup][42][/sup]X-Content-Type-Options: nosniff
X-Powered-By[sup][43][/sup]表明用于支持当前网页应用程序的技术(例如PHP)(版本号细节通常放置在 X-Runtime 或 X-Version 中)X-Powered-By: PHP/5.4.0
X-UA-Compatible[sup][44][/sup]推荐指定的渲染引擎(通常是向后兼容模式)来显示内容。也用于激活 Internet Explorer 中的 Chrome FrameX-UA-Compatible: IE=EmulateIE7

X-UA-Compatible: IE=edge
X-UA-Compatible: Chrome=1
X-Content-Duration[sup][45][/sup]指出音视频的长度,单位为秒。只受Gecko内核浏览器支持。X-Content-Duration: 42.666

回复

使用道具 举报

1万

主题

6万

回帖

10万

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
107221
QQ
 楼主| 发表于 2017-8-7 01:16:31 | 显示全部楼层
Request fields
Header field nameDescriptionExampleStatus
AcceptContent-Types that are acceptable for the response. See Content negotiation.Accept: text/plainPermanent
Accept-CharsetCharacter sets that are acceptable.Accept-Charset: utf-8Permanent
Accept-EncodingList of acceptable encodings. See HTTP compression.Accept-Encoding: gzip, deflatePermanent
Accept-LanguageList of acceptable human languages for response. See Content negotiation.Accept-Language: en-USPermanent
Accept-DatetimeAcceptable version in time.Accept-Datetime: Thu, 31 May 2007 20:35:00 GMTProvisional
Access-Control-Request-Method,
Access-Control-Request-Headers[7]
Initiates a request for cross-origin resource sharing with Origin (below).Access-Control-Request-Method: GETPermanent: standard
AuthorizationAuthentication credentials for HTTP authentication.Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==Permanent
Cache-ControlUsed to specify directives that must be obeyed by all caching mechanisms along the request-response chain.Cache-Control: no-cachePermanent
ConnectionControl options for the current connection and list of hop-by-hop request fields.[8]
Must not be used with HTTP/2.[9]
Connection: keep-alive
Connection: Upgrade
Permanent
CookieAn HTTP cookie previously sent by the server with Set-Cookie (below).Cookie: $Version=1; Skin=new;Permanent: standard
Content-LengthThe length of the request body in octets (8-bit bytes).Content-Length: 348Permanent
Content-MD5A Base64-encoded binary MD5 sum of the content of the request body.Content-MD5: Q2hlY2sgSW50ZWdyaXR5IQ==Obsolete[10]
Content-TypeThe MIME type of the body of the request (used with POST and PUT requests).Content-Type: application/x-www-form-urlencodedPermanent
DateThe date and time that the message was originated (in "HTTP-date" format as defined by RFC 7231 Date/Time Formats).Date: Tue, 15 Nov 1994 08:12:31 GMTPermanent
ExpectIndicates that particular server behaviors are required by the client.Expect: 100-continuePermanent
ForwardedDisclose original information of a client connecting to a web server through an HTTP proxy.[11]Forwarded: for=192.0.2.60;proto=http;by=203.0.113.43Forwarded: for=192.0.2.43, for=198.51.100.17Permanent
FromThe email address of the user making the request.From: user@example.comPermanent
HostThe domain name of the server (for virtual hosting), and the TCP port number on which the server is listening. The port number may be omitted if the port is the standard port for the service requested.
Mandatory since HTTP/1.1.[12] If the request is generated directly in HTTP/2, it should not be used.[13]
Host: en.wikipedia.org:8080
Host: en.wikipedia.org
Permanent
If-MatchOnly perform the action if the client supplied entity matches the same entity on the server. This is mainly for methods like PUT to only update a resource if it has not been modified since the user last updated it.If-Match: "737060cd8c284d8af7ad3082f209582d"Permanent
If-Modified-SinceAllows a 304 Not Modified to be returned if content is unchanged.If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMTPermanent
If-None-MatchAllows a 304 Not Modified to be returned if content is unchanged, see HTTP ETag.If-None-Match: "737060cd8c284d8af7ad3082f209582d"Permanent
If-RangeIf the entity is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity.If-Range: "737060cd8c284d8af7ad3082f209582d"Permanent
If-Unmodified-SinceOnly send the response if the entity has not been modified since a specific time.If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMTPermanent
Max-ForwardsLimit the number of times the message can be forwarded through proxies or gateways.Max-Forwards: 10Permanent
Origin[7]Initiates a request for cross-origin resource sharing (asks server for Access-Control-* response fields).Origin: http://www.example-social-network.comPermanent: standard
PragmaImplementation-specific fields that may have various effects anywhere along the request-response chain.Pragma: no-cachePermanent
Proxy-AuthorizationAuthorization credentials for connecting to a proxy.Proxy-Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==Permanent
RangeRequest only part of an entity. Bytes are numbered from 0. See Byte serving.Range: bytes=500-999Permanent
Referer [sic]This is the address of the previous web page from which a link to the currently requested page was followed. (The word “referrer” has been misspelled in the RFC as well as in most implementations to the point that it has become standard usage and is considered correct terminology)Referer: http://en.wikipedia.org/wiki/Main_PagePermanent
TEThe transfer encodings the user agent is willing to accept: the same values as for the response header field Transfer-Encoding can be used, plus the "trailers" value (related to the "chunked" transfer method) to notify the server it expects to receive additional fields in the trailer after the last, zero-sized, chunk.
Only trailers is supported in HTTP/2.[9]
TE: trailers, deflatePermanent
User-AgentThe user agent string of the user agent.User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0Permanent
UpgradeAsk the server to upgrade to another protocol.
Must not be used to upgrade to HTTP/2.[9]
Upgrade: HTTPS/1.3, IRC/6.9, RTA/x11, websocketPermanent
ViaInforms the server of proxies through which the request was sent.Via: 1.0 fred, 1.1 example.com (Apache/1.1)Permanent
WarningA general warning about possible problems with the entity body.Warning: 199 Miscellaneous warningPermanent
Common non-standard request fields
Field nameDescriptionExample
X-Requested-WithMainly used to identify Ajax requests. Most JavaScript frameworks send this field with value of XMLHttpRequestX-Requested-With: XMLHttpRequest
DNT[14]Requests a web application to disable their tracking of a user. This is Mozilla's version of the X-Do-Not-Track header field (since Firefox 4.0 Beta 11). Safari and IE9 also have support for this field.[15]On March 7, 2011, a draft proposal was submitted to IETF.[16] The W3C Tracking Protection Working Group is producing a specification.[17]DNT: 1 (Do Not Track Enabled)
DNT: 0 (Do Not Track Disabled)
X-Forwarded-For[18]A de facto standard for identifying the originating IP address of a client connecting to a web server through an HTTP proxy or load balancerX-Forwarded-For: client1, proxy1, proxy2
X-Forwarded-For: 129.78.138.66, 129.78.64.103
X-Forwarded-Host[19]A de facto standard for identifying the original host requested by the client in the Host HTTP request header, since the host name and/or port of the reverse proxy (load balancer) may differ from the origin server handling the request.X-Forwarded-Host: en.wikipedia.org:8080
X-Forwarded-Host: en.wikipedia.org
X-Forwarded-Proto[20]A de facto standard for identifying the originating protocol of an HTTP request, since a reverse proxy (or a load balancer) may communicate with a web server using HTTP even if the request to the reverse proxy is HTTPS. An alternative form of the header (X-ProxyUser-Ip) is used by Google clients talking to Google servers.X-Forwarded-Proto: https
Front-End-Https[21]Non-standard header field used by Microsoft applications and load-balancersFront-End-Https: on
X-Http-Method-Override[22]Requests a web application to override the method specified in the request (typically POST) with the method given in the header field (typically PUT or DELETE). This can be used when a user agent or firewall prevents PUT or DELETE methods from being sent directly (note that this is either a bug in the software component, which ought to be fixed, or an intentional configuration, in which case bypassing it may be the wrong thing to do).X-HTTP-Method-Override: DELETE
X-ATT-DeviceId[23]Allows easier parsing of the MakeModel/Firmware that is usually found in the User-Agent String of AT&T DevicesX-Att-Deviceid: GT-P7320/P7320XXLPG
X-Wap-Profile[24]Links to an XML file on the Internet with a full description and details about the device currently connecting. In the example to the right is an XML file for an AT&T Samsung Galaxy S2.x-wap-profile:http://wap.samsungmobile.com/uaprof/SGH-I777.xml
Proxy-Connection[25]Implemented as a misunderstanding of the HTTP specifications. Common because of mistakes in implementations of early HTTP versions. Has exactly the same functionality as standard Connection field.
Must not be used with HTTP/2.[9]
Proxy-Connection: keep-alive
X-UIDH[26][27][28]Server-side deep packet insertion of a unique ID identifying customers of Verizon Wireless; also known as "perma-cookie" or "supercookie"X-UIDH: ...
X-Csrf-Token[29]Used to prevent cross-site request forgery. Alternative header names are: X-CSRFToken[30] and X-XSRF-TOKEN[31]X-Csrf-Token: i8XNjC4b8KVok4uw5RftR38Wgp2BFwql
X-Request-ID,
X-Correlation-ID[32]
Correlates HTTP requests between a client and server.X-Request-ID: f058ebd6-02f7-4d3f-942e-904344e8cde5

Response fields
Field nameDescriptionExampleStatus
Access-Control-Allow-Origin,
Access-Control-Allow-Credentials,
Access-Control-Expose-Headers,
Access-Control-Max-Age,
Access-Control-Allow-Methods,
Access-Control-Allow-Headers[7]
Specifying which web sites can participate in cross-origin resource sharingAccess-Control-Allow-Origin: *Permanent: standard
Accept-Patch[33]Specifies which patch document formats this server supportsAccept-Patch: text/example;charset=utf-8Permanent
Accept-RangesWhat partial content range types this server supports via byte servingAccept-Ranges: bytesPermanent
AgeThe age the object has been in a proxy cache in secondsAge: 12Permanent
AllowValid methods for a specified resource. To be used for a 405 Method not allowedAllow: GET, HEADPermanent
Alt-Svc[34]A server uses "Alt-Svc" header (meaning Alternative Services) to indicate that its resources can also be accessed at a different network location (host or port) or using a different protocol
When using HTTP/2, servers should instead send an ALTSVC frame. [35]
Alt-Svc: http/1.1="http2.example.com:8001"; ma=7200Permanent
Cache-ControlTells all caching mechanisms from server to client whether they may cache this object. It is measured in secondsCache-Control: max-age=3600Permanent
ConnectionControl options for the current connection and list of hop-by-hop response fields.[8]
Must not be used with HTTP/2.[9]
Connection: closePermanent
Content-Disposition[36]An opportunity to raise a "File Download" dialogue box for a known MIME type with binary format or suggest a filename for dynamic content. Quotes are necessary with special characters.Content-Disposition: attachment; filename="fname.ext"Permanent
Content-EncodingThe type of encoding used on the data. See HTTP compression.Content-Encoding: gzipPermanent
Content-LanguageThe natural language or languages of the intended audience for the enclosed content[37]Content-Language: daPermanent
Content-LengthThe length of the response body in octets (8-bit bytes)Content-Length: 348Permanent
Content-LocationAn alternate location for the returned dataContent-Location: /index.htmPermanent
Content-MD5A Base64-encoded binary MD5 sum of the content of the responseContent-MD5: Q2hlY2sgSW50ZWdyaXR5IQ==Obsolete[10]
Content-RangeWhere in a full body message this partial message belongsContent-Range: bytes 21010-47021/47022Permanent
Content-TypeThe MIME type of this contentContent-Type: text/html; charset=utf-8Permanent
DateThe date and time that the message was sent (in "HTTP-date" format as defined by RFC 7231) [38]Date: Tue, 15 Nov 1994 08:12:31 GMTPermanent
ETagAn identifier for a specific version of a resource, often a message digestETag: "737060cd8c284d8af7ad3082f209582d"Permanent
ExpiresGives the date/time after which the response is considered stale (in "HTTP-date" format as defined by RFC 7231)Expires: Thu, 01 Dec 1994 16:00:00 GMTPermanent: standard
Last-ModifiedThe last modified date for the requested object (in "HTTP-date" format as defined by RFC 7231)Last-Modified: Tue, 15 Nov 1994 12:45:26 GMTPermanent
LinkUsed to express a typed relationship with another resource, where the relation type is defined by RFC 5988Link: </feed>; rel="alternate"[39]Permanent
LocationUsed in redirection, or when a new resource has been created.Location: http://www.w3.org/pub/WWW/People.htmlPermanent
P3PThis field is supposed to set P3P policy, in the form of P3P:CP="your_compact_policy". However, P3P did not take off,[40] most browsers have never fully implemented it, a lot of websites set this field with fake policy text, that was enough to fool browsers the existence of P3P policy and grant permissions for third party cookies.P3P: CP="This is not a P3P policy! See http://www.google.com/support/ac ... p;amp;answer=151657 for more info."Permanent
PragmaImplementation-specific fields that may have various effects anywhere along the request-response chain.Pragma: no-cachePermanent
Proxy-AuthenticateRequest authentication to access the proxy.Proxy-Authenticate: BasicPermanent
Public-Key-Pins[41]HTTP Public Key Pinning, announces hash of website's authentic TLS certificatePublic-Key-Pins: max-age=2592000; pin-sha256="E9CZ9INDbd+2eRQozYqqbQ2yXLVKB9+xcprMF+44U1g=";Permanent
Retry-AfterIf an entity is temporarily unavailable, this instructs the client to try again later. Value could be a specified period of time (in seconds) or a HTTP-date.[42]
    [li]Example 1: Retry-After: 120[/li][li]Example 2: Retry-After: Fri, 07 Nov 2014 23:59:59 GMT[/li]

Permanent
ServerA name for the serverServer: Apache/2.4.1 (Unix)Permanent
Set-CookieAn HTTP cookieSet-Cookie: UserID=JohnDoe; Max-Age=3600; Version=1Permanent: standard
Strict-Transport-SecurityA HSTS Policy informing the HTTP client how long to cache the HTTPS only policy and whether this applies to subdomains.Strict-Transport-Security: max-age=16070400; includeSubDomainsPermanent: standard
TrailerThe Trailer general field value indicates that the given set of header fields is present in the trailer of a message encoded with chunked transfer coding.Trailer: Max-ForwardsPermanent
Transfer-EncodingThe form of encoding used to safely transfer the entity to the user. Currently defined methods are: chunked, compress, deflate, gzip, identity.
Must not be used with HTTP/2.[9]
Transfer-Encoding: chunkedPermanent
TkTracking Status header, value suggested to be sent in response to a DNT(do-not-track), possible values:"!" — under construction"?" — dynamic"G" — gateway to multiple parties"N" — not tracking"T" — tracking"C" — tracking with consent&quot" — tracking only if consented"D" — disregarding DNT"U" — updatedTk: ?Permanent
UpgradeAsk the client to upgrade to another protocol.
Must not be used to upgrade to HTTP/2[9]
Upgrade: HTTPS/1.3, IRC/6.9, RTA/x11, websocketPermanent
VaryTells downstream proxies how to match future request headers to decide whether the cached response can be used rather than requesting a fresh one from the origin server.
    [li]Example 1: Vary: *[/li][li]Example 2: Vary: Accept-Language[/li]
Permanent
ViaInforms the client of proxies through which the response was sent.Via: 1.0 fred, 1.1 example.com (Apache/1.1)Permanent
WarningA general warning about possible problems with the entity body.Warning: 199 Miscellaneous warningPermanent
WWW-AuthenticateIndicates the authentication scheme that should be used to access the requested entity.WWW-Authenticate: BasicPermanent
X-Frame-Options[43]Clickjacking protection: deny - no rendering within a frame, sameorigin - no rendering if origin mismatch, allow-from - allow from specified location, allowall - non-standard, allow from any locationX-Frame-Options: denyObsolete[44]

Common non-standard response fields
Field nameDescriptionExample
Content-Security-Policy,
X-Content-Security-Policy,
X-WebKit-CSP[45]
Content Security Policy definition.X-WebKit-CSP: default-src 'self'
RefreshUsed in redirection, or when a new resource has been created. This refresh redirects after 5 seconds. Header extension introduced by Netscape and supported by most web browsers.Refresh: 5; url=http://www.w3.org/pub/WWW/People.html
StatusCGI header field specifying the status of the HTTP response. Normal HTTP responses use a separate "Status-Line" instead, defined by RFC 7230.[46]Status: 200 OK
Upgrade-Insecure-Requests[47]Tells a server which (presumably in the middle of a HTTP -> HTTPS migration) hosts mixed content that the client would prefer redirection to HTTPS and can handle Content-Security-Policy: upgrade-insecure-requests
Must not be used with HTTP/2[9]
Upgrade-Insecure-Requests: 1
X-Content-Duration[48]Provide the duration of the audio or video in seconds; only supported by Gecko browsersX-Content-Duration: 42.666
X-Content-Type-Options[49]The only defined value, "nosniff", prevents Internet Explorer from MIME-sniffing a response away from the declared content-type. This also applies to Google Chrome, when downloading extensions.[50]X-Content-Type-Options: nosniff[51]
X-Powered-By[52]Specifies the technology (e.g. ASP.NET, PHP, JBoss) supporting the web application (version details are often in X-Runtime, X-Version, or X-AspNet-Version)X-Powered-By: PHP/5.4.0
X-Request-ID,
X-Correlation-ID[53]
Correlates HTTP requests between a client and server.X-Request-ID: f058ebd6-02f7-4d3f-942e-904344e8cde5
X-UA-Compatible[54]Recommends the preferred rendering engine (often a backward-compatibility mode) to use to display the content. Also used to activate Chrome Frame in Internet Explorer.X-UA-Compatible: IE=EmulateIE7
X-UA-Compatible: IE=edge
X-UA-Compatible: Chrome=1
X-XSS-Protection[55]Cross-site scripting (XSS) filterX-XSS-Protection: 1; mode=block

回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

QQ|小黑屋|Archiver|手机版|硬汉嵌入式论坛

GMT+8, 2024-5-22 11:16 , Processed in 0.251444 second(s), 25 queries .

Powered by Discuz! X3.4 Licensed

Copyright © 2001-2023, Tencent Cloud.

快速回复 返回顶部 返回列表