…ource o operation resource o target resource The following term is defined in [ RFC7230 ] and is not redefined here: o request URI The following terms are used throughout this document: access control: A security feature provided by the server that allows an administrator to rest…

…ndards Track [Page 3] RFC 7541 HPACK May 2015 . Introduction In HTTP/1.1 (see [ RFC7230 ]), header fields are not compressed. As web pages have grown to require dozens to hundreds of requests, the redundant header fields in these requests unnecessarily consume bandwidth, measurab…

…ddresses . . . . . . . . . . . . . . . . . . . . . . . 16 . Introduction HTTP [ RFC7230 ] status codes are sometimes not sufficient to convey enough information about an error to be helpful. While humans behind Web browsers can be informed about the nature of the problem with an …

…ion "#rule" as defined in Section 7 of HTTP/1.1 -- Message Syntax and Routing. [RFC7230] The following core rules are included by reference, as defined in Appendix B.1 of [ABNF] ALPHA (letters), DIGIT (decimal 0-9), WSP (white space) and VCHAR (printing characters). 3. Policy Del…

…rds Track [Page 4] RFC 8471 The Token Binding Protocol Version 1.0 October 2018 RFC7230 ] or HTTP/2 messages [ RFC7540 ]. [ RFC8473 ] also describes Token Binding between multiple communicating parties: User Agent, Identity Provider, and Relying Party. . Token Binding Protocol Me…

…ion Sequence: 0x68 0x74 0x74 0x70 0x2f 0x31 0x2e 0x31 ("http/1.1") Reference: [ RFC7230 Protocol: SPDY/1 Identification Sequence: 0x73 0x70 0x64 0x79 0x2f 0x31 ("spdy/1") Reference: Protocol: SPDY/2 Identification Sequence: 0x73 0x70 0x64 0x79 0x2f 0x32 ("spdy/2") Reference: Frie…

…ion Sequence: 0x68 0x74 0x74 0x70 0x2f 0x31 0x2e 0x31 ("http/1.1") Reference: [ RFC7230 Protocol: SPDY/1 Identification Sequence: 0x73 0x70 0x64 0x79 0x2f 0x31 ("spdy/1") Reference: Protocol: SPDY/2 Identification Sequence: 0x73 0x70 0x64 0x79 0x2f 0x32 ("spdy/2") Reference: Frie…

…ion Sequence: 0x68 0x74 0x74 0x70 0x2f 0x31 0x2e 0x31 ("http/1.1") Reference: [ RFC7230 Protocol: SPDY/1 Identification Sequence: 0x73 0x70 0x64 0x79 0x2f 0x31 ("spdy/1") Reference: Protocol: SPDY/2 Identification Sequence: 0x73 0x70 0x64 0x79 0x2f 0x32 ("spdy/2") Reference: Frie…

…is was sometimes used to implement reactive client authentication in HTTP/1.1 [ RFC7230 ], where the server decides whether to request a client certificate based on the HTTP request. HTTP/2 [ RFC7540 ] multiplexes multiple HTTP requests over a single connection, which is incompat…

…, P., Ed. "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. , and T. Nart…

…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…

…, P., Ed. "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. , and T. Nart…

…s for application protocols in which the client sends data first, such as HTTP [RFC7230]. Figure 1 (copied from [RFC5246]) shows the message flow for a full handshake. Client Server ClientHello --------> ServerHello Certificate* ServerKeyExchange* CertificateRequest* <-------- Se…

…t is referred to as "deflate" for consistency with HTTP Content-Encodings. See [RFC7230] section 4.2.2. Implementations must be "compliant" as described in [RFC1950] section 2.3. Field values described as invalid in [RFC1950] must not be created by CompressionStream , and are err…

… for application protocols in which the client sends data first, such as HTTP [ RFC7230 ]. Figure 1 (copied from [ RFC5246 ]) shows the message flow for a full handshake. Client Server ClientHello --------> ServerHello Certificate* ServerKeyExchange* CertificateRequest* <--------…