…this document) 2. "Semantics and Content" [ RFC7231 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 upd…

…this document) 2. "Semantics and Content" [ RFC7231 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 upd…

…this document) 2. "Semantics and Content" [ RFC7231 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 upd…

…this document) 2. "Semantics and Content" [ RFC7231 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 upd…

…this document) 2. "Semantics and Content" [ RFC7231 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 upd…

…ional DNS caches that do not have such a mechanism. HTTP conditional requests [ RFC7232 ] may be of limited value to DoH, as revalidation provides only a bandwidth benefit and DNS transactions are normally latency bound. Furthermore, the HTTP response header fields that enable re…

…cted a content mismatch in a 304 response and is following the instructions in [RFC7232], Section 4.1 to repeat the request unconditionally, in which case the new request is still basically a direct consequence of the origin request, and the header field should probably be kept. …

…30 B.2 HTTP/1.1 Semantics and Content RFC7231 B.3 HTTP/1.1 Conditional Requests RFC7232 B.4 HTTP/1.1 Range Requests RFC7233 B.5 HTTP/1.1 Authentication RFC7235 B.6 HTTP Status Code 308 (Permanent Redirect) RFC7538 B.7 HTTP Authentication-Info and Proxy-Authentication-Info Respons…

…ng Parties MUST use the "If-Modified-Since" header explained in Section 3.3 of [RFC7232] in requests. If a Relying Party finds that updates are available, it SHOULD download and process the file as described in Section 3.4.1 and initiate a new RPKI object validation process. Howe…

…cted a content mismatch in a 304 response and is following the instructions in [RFC7232], Section 4.1 to repeat the request unconditionally, in which case the new request is still basically a direct consequence of the origin request, and the header field should probably be kept. …

…B.2 HTTP/1.1 Semantics and Content [RFC7231] B.3 HTTP/1.1 Conditional Requests [RFC7232] B.4 HTTP/1.1 Range Requests [RFC7233] B.5 HTTP/1.1 Authentication [RFC7235] B.6 HTTP Status Code 308 (Permanent Redirect) [RFC7538] B.7 HTTP Authentication-Info and Proxy-Authentication-Info …

…30 B.2 HTTP/1.1 Semantics and Content RFC7231 B.3 HTTP/1.1 Conditional Requests RFC7232 B.4 HTTP/1.1 Range Requests RFC7233 B.5 HTTP/1.1 Authentication RFC7235 B.6 HTTP Status Code 308 (Permanent Redirect) RFC7538 B.7 HTTP Authentication-Info and Proxy-Authentication-Info Respons…

…parameter name etag and a corresponding parameter value identical to the ETag [ RFC7232 of the paged resource For example: Link: <http://example.org/customer-relations>; rel="canonical"; etag="customer-relations-v1" Non-normative note: If the rel="canonical"; etag="..." value cha…

…30 B.2 HTTP/1.1 Semantics and Content RFC7231 B.3 HTTP/1.1 Conditional Requests RFC7232 B.4 HTTP/1.1 Range Requests RFC7233 B.5 HTTP/1.1 Authentication RFC7235 B.6 HTTP Status Code 308 (Permanent Redirect) RFC7538 B.7 HTTP Authentication-Info and Proxy-Authentication-Info Respons…

…cted a content mismatch in a 304 response and is following the instructions in [RFC7232], Section 4.1 to repeat the request unconditionally, in which case the new request is still basically a direct consequence of the origin request, and the header field should probably be kept. …