…ditional GET requests are the most efficient mechanism for HTTP cache updates [ RFC7234 ]. Conditionals can also be applied to state-changing methods, such as PUT and DELETE, to prevent the "lost update" problem: one client accidentally overwriting the work of another client that…
…ditional GET requests are the most efficient mechanism for HTTP cache updates [ RFC7234 ]. Conditionals can also be applied to state-changing methods, such as PUT and DELETE, to prevent the "lost update" problem: one client accidentally overwriting the work of another client that…
…ditional GET requests are the most efficient mechanism for HTTP cache updates [ RFC7234 ]. Conditionals can also be applied to state-changing methods, such as PUT and DELETE, to prevent the "lost update" problem: one client accidentally overwriting the work of another client that…
…ditional GET requests are the most efficient mechanism for HTTP cache updates [ RFC7234 ]. Conditionals can also be applied to state-changing methods, such as PUT and DELETE, to prevent the "lost update" problem: one client accidentally overwriting the work of another client that…
… servers SHOULD assign an explicit HTTP freshness lifetime (see Section 4.2 of [RFC7234] ) so that the DoH client is more likely to use fresh DNS data. This requirement is due to HTTP caches being able to assign their own heuristic freshness (such as that described in Section 4.2…
…7 of [RFC7230] . The rules below are defined in [ RFC5234 ], [ RFC7230 ], and [ RFC7234 ]: OWS = <OWS, see [RFC7230], Section 3.2.3 > delta-seconds = <delta-seconds; see [RFC7234], Section 1.2.1 > port = <port, see [RFC7230], Section 2.7 > quoted-string = <quoted-string, see [RFC…
…. "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…
…RFC7231] "Conditional Requests" [RFC7232] "Range Requests" [RFC7233] "Caching" [RFC7234] "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, previous…
…n 7 of [RFC7230] . The rules below are defined in [ RFC5234 ], [ RFC7230 ], and RFC7234 ]: OWS = <OWS, see [RFC7230], Section 3.2.3 delta-seconds = <delta-seconds; see [RFC7234], Section 1.2.1 port = <port, see [RFC7230], Section 2.7 quoted-string = <quoted-string, see [RFC7230],…
…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 challe…
…3. "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, previ…
…. "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…
…. "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…
…. "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…
…. "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…