… (ABNF) notation of [ RFC5234 ] with a list extension, defined in Section 7 of [RFC7230] , that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates repetition). The ABNF production for "auth-param" is defined in S…

…hecks ( [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 messages as well; however, discoverability is not on par with response message…

…ur Form (ABNF) notation of [ RFC5234 ] with the list rule extension defined in [RFC7230], Appendix B . It includes by reference the DIGIT rule from [ RFC5234 ]; the OWS, field-name and quoted-string rules from [ RFC7230 ]; and the parameter rule from [ RFC7231 ]. 2 . Client Hint …

… 04 5 . HTTP Integration This protocol MUST be used with the https URI scheme [ RFC7230 ]. Sections 8 and 9 discuss additional considerations for the integration with HTTP. 5.1 . Cache Interaction A DoH exchange can pass through a hierarchy of caches that include both HTTP- and D…

…//www.example.com/.well-known/example'. This specification updates the "http" [ RFC7230 ] and "https" [ RFC7230 schemes to support well-known URIs. Other existing schemes can use the appropriate process for updating their definitions; for example, RFC8307 ] does so for the "ws" a…

…rds Track in 1997 RFC2068 , revised in 1999 RFC2616 , and revised again in 2014 RFC7230 through RFC7235 ). HTTP/2 ( HTTP/2 ) introduced a multiplexed session layer on top of the existing TLS and TCP protocols for exchanging concurrent HTTP messages with efficient field compressio…

… request constructed from the received data, according to the requirements of [ RFC7230 ]. If it is not possible to construct a complete HTTP request the remote end must either close the connection return an HTTP response with status code 500, or return an error with error code u…

…otocol (RRDP) July 2017 The accessLocation MUST be an HTTPS URI as defined in [ RFC7230 ] that will point to the Update Notification File for the Repository Server that publishes the products of this Certificate Authority certificate. 3.3 . Repository Server Use 3.3.1 . Initializ…

…ck in 1997 [RFC2068] , revised in 1999 [RFC2616] , and revised again in 2014 ( [RFC7230] through [RFC7235] ). HTTP/2 ( [HTTP/2] ) introduced a multiplexed session layer on top of the existing TLS and TCP protocols for exchanging concurrent HTTP messages with efficient field compr…

…rds Track in 1997 RFC2068 , revised in 1999 RFC2616 , and revised again in 2014 RFC7230 through RFC7235 ). HTTP/2 ( HTTP/2 ) introduced a multiplexed session layer on top of the existing TLS and TCP protocols for exchanging concurrent HTTP messages with efficient field compressio…

…rds Track in 1997 RFC2068 , revised in 1999 RFC2616 , and revised again in 2014 RFC7230 through RFC7235 ). HTTP/2 ( HTTP/2 ) introduced a multiplexed session layer on top of the existing TLS and TCP protocols for exchanging concurrent HTTP messages with efficient field compressio…

… Internet Message Format ”, RFC 5322, DOI 10.17487/RFC5322 , October 2008, < >. RFC7230 Fielding, R., Ed. and J. Reschke, Ed., “ Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing ”, RFC 7230, DOI 10.17487/RFC7230 , June 2014, < >. RFC8126 Cotton, M., Leiba, B., a…

…ck in 1997 [RFC2068] , revised in 1999 [RFC2616] , and revised again in 2014 ( [RFC7230] through [RFC7235] ). HTTP/2 ( [HTTP/2] ) introduced a multiplexed session layer on top of the existing TLS and TCP protocols for exchanging concurrent HTTP messages with efficient field compr…

…automatically re-link references to the effective request URI ( Section 5.5 of [RFC7230] ) to one or more of the new references sent by the server, where possible. The server SHOULD generate a Location header field ( [RFC7231], Section 7.1.2 ) in the response containing a preferr…

…rds Track in 1997 RFC2068 , revised in 1999 RFC2616 , and revised again in 2014 RFC7230 through RFC7235 ). HTTP/2 ( HTTP/2 ) introduced a multiplexed session layer on top of the existing TLS and TCP protocols for exchanging concurrent HTTP messages with efficient field compressio…