…. "Conditional Requests" [ RFC7232 4. "Range Requests" [ RFC7233 5. "Caching" [ RFC7234 6. "Authentication" [ RFC7235 This HTTP/1.1 specification obsoletes RFC 2616 and RFC 2145 (on HTTP versioning). This specification also updates the use of CONNECT to establish a tunnel, previo…

…t MUST NOT modify any Authorization fields in that request. See Section 3.2 of [RFC7234] for details of and requirements pertaining to handling of the Authorization field by HTTP caches. 4.3 . Proxy-Authenticate The "Proxy-Authenticate" header field consists of at least one chall…

…t MUST NOT modify any Authorization fields in that request. See Section 3.2 of [RFC7234] for details of and requirements pertaining to handling of the Authorization field by HTTP caches. 4.3 . Proxy-Authenticate The "Proxy-Authenticate" header field consists of at least one chall…

…t MUST NOT modify any Authorization fields in that request. See Section 3.2 of [RFC7234] for details of and requirements pertaining to handling of the Authorization field by HTTP caches. 4.3 . Proxy-Authenticate The "Proxy-Authenticate" header field consists of at least one chall…

…t MUST NOT modify any Authorization fields in that request. See Section 3.2 of [RFC7234] for details of and requirements pertaining to handling of the Authorization field by HTTP caches. 4.3 . Proxy-Authenticate The "Proxy-Authenticate" header field consists of at least one chall…

…t MUST NOT modify any Authorization fields in that request. See Section 3.2 of [RFC7234] for details of and requirements pertaining to handling of the Authorization field by HTTP caches. 4.3 . Proxy-Authenticate The "Proxy-Authenticate" header field consists of at least one chall…

…esource is cacheable, the server MUST also emit a Vary response header field ([ RFC7234 ]), and optionally Key ([ I-D.ietf-httpbis-key ]), to indicate which hints were used and whether the selected response is appropriate for a later request. Further, depending on the used hint, …

…). HTTP 3xx redirects MUST NOT be followed, and HTTP caching (as specified in [ RFC7234 ]) MUST NOT be used. Senders may wish to rate-limit the frequency of attempts to fetch the HTTPS endpoint even if a valid TXT record for the recipient domain exists. In the case where the HTTP…

…试向不支持客户端-服务端交互的服务端提交对象， 服务端 应当 返回 405 Method Not Allowed 响应。 在适当情况下，HTTP 缓存机制 [ RFC7234 ]， 应当 在客户端接收服务端响应时与服务端发送响应至客户端时被遵守。 6.1 客户端寻址 客户端 负责正确地为新活动设定目标地址。 在某种程度上，这取决于客户端的特定实现，但客户端必须注意，服务端只会将新的活动转发给 to bto cc bcc audience 字段中的地址。 粉丝集合 和/或 公共集合 是作为新活动默认目标地址的良好选择。 客户端 应当 查看通过 object…

…., unless otherwise indicated by explicit cache controls (see Section 4.2.2 of [RFC7234] ). 4.2. Content-Range The "Content-Range" header field is sent in a single part 206 (Partial Content) response to indicate the partial range of the selected representation enclosed as the mes…

…t SHOULD result in a 405 Method Not Allowed response. HTTP caching mechanisms [ RFC7234 SHOULD be respected when appropriate, both in clients receiving responses from servers as well as servers sending responses to clients. 6.1 Client Addressing Clients are responsible for addres…

…t SHOULD result in a 405 Method Not Allowed response. HTTP caching mechanisms [ RFC7234 SHOULD be respected when appropriate, both in clients receiving responses from servers as well as servers sending responses to clients. 6.1 Client Addressing Clients are responsible for addres…

…., unless otherwise indicated by explicit cache controls (see Section 4.2.2 of [RFC7234]). 4.2. Content-Range The "Content-Range" header field is sent in a single part 206 (Partial Content) response to indicate the partial range of the selected representation enclosed as the mess…

…s = 1*DIGIT Figure 3: max-age Value Syntax delta-seconds is used as defined in [RFC7234], Section 1.2.1 See Section 2.3.3 for limitations on the range of values for max-age. 2.1.3 . The includeSubDomains Directive The OPTIONAL includeSubDomains directive is a valueless directive …

…s otherwise indicated by the method definition or explicit cache controls (see [RFC7234], Section 4.2.2 ). Note: This status code is similar to 301 (Moved Permanently) [RFC7231], Section 6.4.2 ), except that it does not allow changing the request method from POST to GET. . Deploy…