…ure for HTTP Upgrade Tokens replaces that previously defined in Section 7.2 of [RFC2817]. 8.6.2. Upgrade Token Registration The "HTTP" entry in the upgrade token registry has been updated with the registration below: +-------+----------------------+----------------------+--------…
…istration procedure for HTTP Status Codes previously defined in Section 7.1 of [RFC2817]. 8.2.1. Procedure A registration MUST include the following fields: o Status Code (3 digits) o Short Description o Pointer to specification text Values to be added to the HTTP status code nam…
…ure for HTTP Upgrade Tokens replaces that previously defined in Section 7.2 of [RFC2817] 8.6.2 . Upgrade Token Registration The "HTTP" entry in the upgrade token registry has been updated with the registration below: +-------+----------------------+----------------------+--------…
…ure for HTTP Upgrade Tokens replaces that previously defined in Section 7.2 of [RFC2817] 8.6.2 . Upgrade Token Registration The "HTTP" entry in the upgrade token registry has been updated with the registration below: +-------+----------------------+----------------------+--------…
…istration procedure for HTTP Status Codes previously defined in Section 7.1 of [RFC2817] 8.2.1 . Procedure A registration MUST include the following fields: o Status Code (3 digits) o Short Description o Pointer to specification text Values to be added to the HTTP status code nam…
…istration procedure for HTTP Status Codes previously defined in Section 7.1 of [RFC2817] 8.2.1 . Procedure A registration MUST include the following fields: o Status Code (3 digits) o Short Description o Pointer to specification text Values to be added to the HTTP status code nam…
…istration procedure for HTTP Status Codes previously defined in Section 7.1 of [RFC2817] 8.2.1 . Procedure A registration MUST include the following fields: o Status Code (3 digits) o Short Description o Pointer to specification text Values to be added to the HTTP status code nam…
…ure for HTTP Upgrade Tokens replaces that previously defined in Section 7.2 of [RFC2817] 8.6.2 . Upgrade Token Registration The "HTTP" entry in the upgrade token registry has been updated with the registration below: +-------+----------------------+----------------------+--------…
…ure for HTTP Upgrade Tokens replaces that previously defined in Section 7.2 of [RFC2817] 8.6.2 . Upgrade Token Registration The "HTTP" entry in the upgrade token registry has been updated with the registration below: +-------+----------------------+----------------------+--------…
…tion in such a sequence, if known. The value "Upgrade" is used for TLS upgrade [RFC2817]. Notes: Implementers guide does not include support for HTTP Upgrade [RFC2817]. Errata ID: 3010 Status: Verified Type: Technical Publication Format(s) : TEXT Reported By: Michael Sweet Date R…
…istration procedure for HTTP Status Codes previously defined in Section 7.1 of [RFC2817] 8.2.1 . Procedure A registration MUST include the following fields: o Status Code (3 digits) o Short Description o Pointer to specification text Values to be added to the HTTP status code nam…
…ure for HTTP Upgrade Tokens replaces that previously defined in Section 7.2 of [RFC2817] 8.6.2 . Upgrade Token Registration The "HTTP" entry in the upgrade token registry has been updated with the registration below: +-------+----------------------+----------------------+--------…
…RFC9110, Section 2.5 TLS Transport Layer Security ANY DIGIT.DIGIT (e.g., "1.2") RFC2817 WebSocket The Web Socket Protocol RFC6455 websocket The Web Socket Protocol RFC6455 ][ RFC8441 h2c Hypertext Transfer Protocol version 2 (HTTP/2) (OBSOLETE) RFC9113, Section 3.1 connect-udp Pr…
…istration procedure for HTTP Status Codes previously defined in Section 7.1 of [RFC2817] 8.2.1 . Procedure A registration MUST include the following fields: o Status Code (3 digits) o Short Description o Pointer to specification text Values to be added to the HTTP status code nam…
…istration procedure for HTTP Status Codes previously defined in Section 7.1 of [RFC2817] 9.2.1 . Procedure Values to be added to the HTTP status code name space require IETF Review (see [RFC5226], Section 4.1 ). 9.2.2 . Considerations for New Status Codes When it is necessary to …