…he Operation Proper cache operation preserves the semantics of HTTP transfers ([RFC7231]) while eliminating the transfer of information already held in the cache. Although caching is an entirely OPTIONAL feature of HTTP, it can be assumed that reusing a cached response is desirab…

…ings allow for payload encodings such as for compression or integrity checks ( [RFC7231], Section 3.1.2 ). In particular, the "gzip" content coding ( [RFC7230], Section 4.2 ) is widely used for payload data sent in response messages. Content codings can be used in request message…

…e Operation Proper cache operation preserves the semantics of HTTP transfers ([ RFC7231 ]) while eliminating the transfer of information already held in the cache. Although caching is an entirely OPTIONAL feature of HTTP, it can be assumed that reusing a cached response is desira…

…ndex Authors' Addresses 1. Introduction Conditional requests are HTTP requests [RFC7231] that include one or more header fields indicating a precondition to be tested before applying the method semantics to the target resource. This document defines the HTTP/1.1 conditional reque…

… RFC3986 ]). The history of these status codes is summarized in Section 6.4 of [RFC7231] , which also classifies the existing status codes into four categories. The first of these categories contains the status codes 301 (Moved Permanently), 302 (Found), and 307 (Temporary Redire…

…uest Subscription is initiated by the subscriber making an HTTPS or HTTP POST [ RFC7231 ] request to the hub URL. This request MUST have a Content-Type header of application/x-www-form-urlencoded (described in Section 4.10.22.6 [ HTML5 ]), MUST use UTF-8 [ Encoding ] as the docum…

… RFC3986 ]). The history of these status codes is summarized in Section 6.4 of [RFC7231] , which also classifies the existing status codes into four categories. The first of these categories contains the status codes 301 (Moved Permanently), 302 (Found), and 307 (Temporary Redire…

… RFC3986 ]). The history of these status codes is summarized in Section 6.4 of [RFC7231] , which also classifies the existing status codes into four categories. The first of these categories contains the status codes 301 (Moved Permanently), 302 (Found), and 307 (Temporary Redire…

… RFC3986 ]). The history of these status codes is summarized in Section 6.4 of [RFC7231] , which also classifies the existing status codes into four categories. The first of these categories contains the status codes 301 (Moved Permanently), 302 (Found), and 307 (Temporary Redire…

… RFC3986 ]). The history of these status codes is summarized in Section 6.4 of [RFC7231] , which also classifies the existing status codes into four categories. The first of these categories contains the status codes 301 (Moved Permanently), 302 (Found), and 307 (Temporary Redire…

… RFC3986 ]). The history of these status codes is summarized in Section 6.4 of [RFC7231] , which also classifies the existing status codes into four categories. The first of these categories contains the status codes 301 (Moved Permanently), 302 (Found), and 307 (Temporary Redire…

… RFC3986 ]). The history of these status codes is summarized in Section 6.4 of [RFC7231] , which also classifies the existing status codes into four categories. The first of these categories contains the status codes 301 (Moved Permanently), 302 (Found), and 307 (Temporary Redire…

…onal Requests June 2014 . Introduction Conditional requests are HTTP requests [ RFC7231 ] that include one or more header fields indicating a precondition to be tested before applying the method semantics to the target resource. This document defines the HTTP/1.1 conditional requ…

…onal Requests June 2014 . Introduction Conditional requests are HTTP requests [ RFC7231 ] that include one or more header fields indicating a precondition to be tested before applying the method semantics to the target resource. This document defines the HTTP/1.1 conditional requ…

…onal Requests June 2014 . Introduction Conditional requests are HTTP requests [ RFC7231 ] that include one or more header fields indicating a precondition to be tested before applying the method semantics to the target resource. This document defines the HTTP/1.1 conditional requ…