…rameter Name: A name for the parameter, which conforms to the "token" grammar [ RFC7230 Purpose (optional): Brief text identifying the purpose of the parameter Header Field(s): The header field(s) in which the parameter can be used Specification: A link to the specification that …
…, 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…
…10.17487/RFC6520, February 2012, < https://www.rfc-editor.org/info/rfc6520 >. [ 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, < https://www.rfc-editor.org/info/rfc…
…ty (TLS) [ RFC5246 ]. For the HTTP protocol, this means using "https://" URLs [ RFC7230 ]. In the past, Web sites have deployed HTTPS rarely; often, only when financial transactions take place. More recently, however, it has become apparent that nearly all activity on the Web can…
…986 ] and a specific URI scheme [ IANA-URI-SCHEMES ], such as the http scheme [ RFC7230 ]. In addition to defining a specific DID scheme , a DID method specification also defines the mechanisms for creating, resolving, updating, and deactivating DIDs and DID documents using a spe…
…10.17487/RFC6520, February 2012, < https://www.rfc-editor.org/info/rfc6520 >. [ 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, < https://www.rfc-editor.org/info/rfc…
… link. Line breaks must not be used in Link headers as they are not allowed per RFC7230 ; only whitespaces and tabs are supported as separators. The below examples show responses to an HTTP GET request issued against the URI of the landing page of our fictitious scholarly object.…
US
rfc8446
https://www.rfc-editor.org/rfc/inline-errata/rfc8446.html
…OI 10.17487/RFC6520, February 2012, <https://www.rfc-editor.org/info/rfc6520>. [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, <https://www.rfc-editor.org/info/rfc723…
…y (DTLS) Heartbeat Extension", RFC 6520 DOI 10.17487/RFC6520, February 2012, >. 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, >. Rescorla Standards Track [Page 117…
…OI 10.17487/RFC6520, February 2012, <https://www.rfc-editor.org/info/rfc6520>. [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, <https://www.rfc-editor.org/info/rfc723…
…in the request line and prior to the ':' delimiter of any request header lines. RFC7230 Section 3.5 calls out some of these whitespace exceptions, and section 3.2.3 eliminated and clarified the role of implied whitespace in the grammer of this specification. Section 3.1.1 require…
…y (DTLS) Heartbeat Extension", RFC 6520 DOI 10.17487/RFC6520, February 2012, >. 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, >. Rescorla Standards Track [Page 117…
…Date Verified: 2015-01-17 Section A. C & A. D says: field-name = <comment, see [RFC7230], Section 3.2> It should say: field-name = <field-name, see [RFC7230], Section 3.2> Notes: field-name does not follow the `comment` production. The section number is correct. RFC 7232 , "Hyper…
…Date Verified: 2015-01-17 Section A. C & A. D says: field-name = <comment, see [RFC7230], Section 3.2> It should say: field-name = <field-name, see [RFC7230], Section 3.2> Notes: field-name does not follow the `comment` production. The section number is correct. RFC 7232 , "Hyper…
← Previous
Page 9