HTTP Response Headers
Constants
ACCEPT (24)
Acceptable media types.
ACCEPT-CHARSET (25)
Acceptable character sets.
ACCEPT-ENCODING (26)
Acceptable content-coding values.
ACCEPT-LANGUAGE (27)
Acceptable natural languages.
ACCEPT-RANGES (42)
Types of range requests that are accepted.
AGE (48)
An estimate of the amount of time since the response was generated at the origin server.
ALLOW (7)
Methods supported by the server.
AUTHORIZATION (28)
Authorization credentials used for a request.
CACHE-CONTROL (49)
Cache control directives.
CONNECTION (23)
Options that are specified for a particular connection and must not be communicated by proxies over further connections.
CONTENT-BASE (50)
Base Uniform Resource Identifier (URI) for resolving relative URLs within the entity.
CONTENT-DESCRIPTION (4)
Obsolete. Maintained for legacy application compatibility only.
CONTENT-DISPOSITION (47)
Obsolete. Maintained for legacy application compatibility only.
CONTENT-ENCODING (29)
Any additional content codings that have been applied to the entire resource.
CONTENT-ID (3)
Content identification.
CONTENT-LANGUAGE (6)
Language in which the content is presented.
CONTENT-LENGTH (5)
Size of the resource, in bytes.
CONTENT-LOCATION (51)
Resource location for the entity enclosed in the message.
CONTENT-MD5 (52)
MD5 digest of the entity-body for the purpose of providing an end-to-end message integrity check (MIC) for the entity-body. For more information, see RFC1864, The Content-MD5 Header Field, at http://ftp.isi.edu/in-notes/rfc1864.txt .
CONTENT-RANGE (53)
Location in the full entity-body where the partial entity-body should be inserted and the total size of the full entity-body.
CONTENT-TRANSFER_ENCODING (2)
Additional content coding that has been applied to the resource.
CONTENT-TYPE (1)
Content type of the resource (such as text/html).
COOKIE (44)
Cookies associated with the request.
COST (15)
Not supported.
DATE (9)
Date and time at which the message was originated.
DERIVED-FROM (14)
Not supported.
ECHO-HEADERS (73)
Not implemented.
ECHO-HEADERS-CRLF (74)
Not implemented.
ECHO-REPLY (72)
Not implemented.
ECHO-REQUEST (71)
Not implemented.
ETAG (54)
Entity tag for the associated entity.
EXPECT (68)
Expect header, which indicates whether the client application should expect 100 series responses.
EXPIRES (10)
Date and time after which the resource should be considered outdated.
FORWARDED (30)
Obsolete. Maintained for legacy application compatibility only.
FROM (31)
E-mail address for the human user who controls the requesting user agent if the From header is given.
HOST (55)
Internet host and port number of the resource being requested.
IF-MATCH (56)
Contents of the If-Match request-header field.
IF-MODIFIED-SINCE (32)
Contents of the If-Modified-Since header.
IF-NONE-MATCH (57)
Contents of the If-None-Match request-header field.
IF-RANGE (58)
Contents of the If-Range request-header field. This header allows the client application to check if the entity related to a partial copy of the entity in the client application's cache has not been updated. If the entity has not been updated, send the parts that the client application is missing. If the entity has been updated, send the entire updated entity.
IF-UNMODIFIED-SINCE (59)
Contents of the If-Unmodified-Since request-header field.
LAST-MODIFIED (11)
Date and time at which the server believes the resource was last modified.
LINK (16)
Obsolete. Maintained for legacy application compatibility only.
LOCATION (33)
Absolute URI.
MAX (75)
Not a query flag. Indicates the maximum value of an * value.
MAX-FORWARDS (60)
Number of proxies or gateways that can forward the request to the next inbound server.
MESSAGE-ID (12)
Not supported.
MIME-VERSION (0)
Version of the MIME protocol that was used to construct the message.
MSTHEMECOMPATIBLE
Internet Explorer 6 and later. Disables theming support for a Web page. The content attribute of the meta element must be set to no.
ORIG-URI (34)
Obsolete. Maintained for legacy application compatibility only.
PRAGMA (17)
Implementation-specific directives that might apply to any recipient along the request/response chain.
PROXY-AUTHENTICATE (41)
Authentication scheme and realm returned by the proxy.
PROXY-AUTHORIZATION (61)
Header that is used to identify the user to a proxy that requires authentication. This header can only be retrieved before the request is sent to the server.
PROXY-CONNECTION (69)
Proxy-Connection header.
PUBLIC (8)
Methods available at this server.
RANGE (62)
Byte range of an entity.
RAW-HEADERS (21)
All the headers returned by the server. Each header is terminated by "/0". An additional "/0" terminates the list of headers.
RAW-HEADERS-CRLF (22)
All the headers returned by the server. Each header is separated by a carriage return/line feed (CR/LF) sequence.
REFERER (35)
URI of the resource where the requested URI was obtained.
REFRESH (46)
Obsolete. Maintained for legacy application compatibility only.
REQUEST-METHOD (45)
Verb that is used in the request, typically GET or POST.
RETRY-AFTER (36)
Amount of time the service is expected to be unavailable.
SERVER (37)
Information about the software used by the origin server to handle the request.
SET-COOKIE (43)
Value of the cookie set for the request.
STATUS-CODE (19)
Status code returned by the server. For a list of possible values, see HTTP Status Codes.
STATUS-TEXT (20)
Any additional text returned by the server on the response line.
TITLE (38)
Obsolete. Maintained for legacy application compatibility only.
TRANSFER-ENCODING (63)
Type of transformation that has been applied to the message body so it can be safely transferred between the sender and recipient.
UNLESS-MODIFIED-SINCE (70)
Unless-Modified-Since header.
UPGRADE (64)
Additional communication protocols that are supported by the server.
URI (13)
Some or all of the URIs by which the Request-URI resource can be identified.
USER-AGENT (39)
Information about the user agent that made the request.
VARY (65)
Header that indicates that the entity was selected from a number of available representations of the response using server-driven negotiation.
VERSION (18)
Last response code returned by the server.
VIA (66)
Intermediate protocols and recipients between the user agent and the server on requests, and between the origin server and the client on responses.
WARNING (67)
Additional information about the status of a response that might not be reflected by the response status code.
WWW-AUTHENTICATE (40)
Authentication scheme and realm returned by the server.
Remarks
A response header can be created using the HTTP-EQUIV attribute of the meta tag.
Corresponding values are provided for use with HttpQueryInfo and QueryInfo
分享到:
相关推荐
### Response-Headers详解 #### HTTP响应报头的基本概念与作用 HTTP响应报头是Web服务器向客户端(通常是浏览器)发送响应时附带的信息。这些报头提供了关于响应本身的元数据,如响应的内容类型、长度等,对于正确...
本篇文章将详细讲解如何在Unity3D中使用`www`类进行HTTP请求,并且重点讨论如何进行Headers验证。 Unity3D中的`WWW`类是用于发送HTTP和HTTPS请求的基础类,它简化了与Web服务的通信。当你需要从服务器获取数据或...
"Started At"显示请求开始的时间,"Connect"显示连接到的IP地址,"Http Request"和"Http Response Headers and content"分别揭示了请求信息和服务器响应的头部信息。 "Header"(报头)部分则详细列出了从Web服务器...
用 golang 写 http server 时,可以很方便可通过 w.Header.Set(k, v) 来设置 http response 中 header 的内容。但是需要特别注意的是:某些时候不仅要修改 response的header ,还要修改 response的StatusCode。修改...
1. 了解HTTP响应头(HTTP Response Headers)的作用: - 在Web开发中,服务器响应客户端请求时会携带一系列的HTTP头部信息,其中和文件下载直接相关的是“Content-Type”和“Content-Disposition”。 - “Content-...
3. **Fiddler.HTTPRequestHeaders 和 HTTPResponseHeaders 类** 这两个类分别代表了HTTP请求和响应的头部信息。它们提供了方便的方法来获取、设置或删除头部字段。例如,你可以通过`HTTPRequestHeaders["User-Agent...
和 `HttpResponseHeaders`:HTTP请求和响应头的类。 41. `System.Net.WebHeaderCollection`:HTTP头集合类,存储HTTP请求和响应头。 42. `System.Text.Encodings.Web.HtmlEncoder`:HTML编码类,用于HTML实体编码...
This class is a concrete implementation of StreamLoader that uses a CacheResult as the source for the stream. The CacheResult stored mimetype and encoding is added to the HTTP response headers.
response = requests.get('http://example.com', headers=headers, cookies=cookies) # 提取headers和cookies request_headers = response.request.headers response_headers = response.headers received_cookies ...
response['Access-Control-Expose-Headers'] = "Cookie" ``` 这样,前端就能在接收到响应后访问到名为`Cookie`的自定义header。在Vue中,我们可以这样获取它: ```javascript this.$http.post("/xx/xxx", { tel: ...
1 Introduction 3 1.1 Overview . . . . . . . . ....1.2 History ....1.3 Getting involved ....1.4 License ....2.1 Windows installer ....2.2 Windows binary ....2.3 Mac OS X installer ....2.4 Mac OS X binary ....
在IT行业中,网络通信是核心部分之一,而`request`和`response`是HTTP协议中的两个基本概念,它们构成了客户端(如浏览器)与服务器端之间交互数据的核心机制。本篇文章将深入探讨这两个概念以及它们在实际开发中的...
response = requests.get(url, headers=headers) print(response.content) ``` 在上面的代码中,我们使用了 requests 库来发送 GET 请求,并将 headers 设置为模拟浏览器的 headers 信息。这样,我们可以避免服务器...
for Header in IdHTTP.Response.Headers.Fields do Writeln(Header.Name + ': ' + Header.Value); ``` 更高级的使用场景,比如设置自定义认证、处理Cookie、代理设置等,也可以通过IdHTTP的Request和Response属性...
上述代码示例提供了一个简单的HTTP报文解析器的起点,但它可能并不完整或完全符合所有标准,实际项目中应考虑使用更成熟的库,如`System.Net.Http.Headers.HttpResponseHeaders`,它提供了更强大且健壮的报头解析...
- **响应头(Response Headers)**:服务器返回给客户端的信息,如Content-Type(资源类型)、Content-Length(内容长度)、Date(响应生成的日期和时间)等。 - **实体内容**:响应体,即服务器返回给客户端的...