Subject: [hybi] [Errata Rejected] RFC6455 (5453)

From: RFC Errata System <[email-masked]>
Date: Thu, 20 Sep 2018 05:34:43 -0700 (PDT)

The following errata report has been rejected for RFC6455,
"The WebSocket Protocol".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5453

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Julian Reschke <[email-masked]>
Date Reported: 2018-08-08
Rejected by: Alexey Melnikov (IESG)

Section: 4.1

Original Text
-------------
   2.  If the response lacks an |Upgrade| header field or the |Upgrade|
       header field contains a value that is not an ASCII case-
       insensitive match for the value "websocket", the client MUST
       _Fail the WebSocket Connection_.

Corrected Text
--------------
   2.  If the response lacks an |Upgrade| header field or the |Upgrade|
       header field contains a value that does not match "WebSocket",
       the client MUST _Fail the WebSocket Connection_.

Notes
-----
HTTP upgrade tokens are case-sensitive, and the token registered by RFC 6455 is "WebSocket" (see <https://www.iana.org/assignments/http-upgrade-tokens/http-upgrade-tokens.xhtml>). Examples should be adjusted accordingly.

If stricter checks actually break the protocol, an alternative would be to register more variants of the token, such as "websocket".
 --VERIFIER NOTES-- 
   See <https://www.rfc-editor.org/errata/eid5498>. Implementations seem to be using "websocket", as shown in all examples in this RFC.

--------------------------------------
RFC6455 (draft-ietf-hybi-thewebsocketprotocol-17)
--------------------------------------
Title               : The WebSocket Protocol
Publication Date    : December 2011
Author(s)           : I. Fette, A. Melnikov
Category            : PROPOSED STANDARD
Source              : BiDirectional or Server-Initiated HTTP APP
Area                : Applications
Stream              : IETF
Verifying Party     : IESG