[Bug 23576] Clarify what to do when received null value subprotocol in reply to non-empty subprotocol

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23576

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ian@hixie.ch

--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
(In reply to Takeshi Yoshino from comment #0)
> 
> > The connection will only be established if the server reports that it has 
> > selected one of these subprotocols.
> 
> Though this may be intended to explain the role of the protocols argument
> briefly and non-normatively, we interpreted that this text adds a
> requirement that a WebSocket client MUST abort connection establishment if
> the peer server doesn't select any subprotocol offered by the client.

You interpreted this text incorrectly; it's non-normative. You can tell because
it doesn't contain any normative statements — in particular, the word "must"
isn't there.


> RFC 6455 itself doesn't require a client to abort connection establishment.

Wow, yeah. Huh. Looks like they broke that.

I've added normative text to the HTML spec to fix it.


> RFC 6455 is incomplete about subprotocol validation. It specifies the
> WebSocket protocol layer to fail on the following cases: [...]

Yeah, looks like they broke it between when I edited the spec and when it
became an RFC. Going to the IETF was such a mistake.

Thanks for catching this.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 21 October 2013 17:10:14 UTC