Return close code 1015 to JS when TLS setup fails

NEW
Unassigned

Status

()

Core
Networking: WebSockets
5 years ago
2 years ago

People

(Reporter: jduell, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-would-take])

RFC 6455 section 7.4.1 says we should use 1015 to "indicate that the connection was closed due to a failure to perform a TLS handshake (e.g., the server certificate can't be verified)."

One of the later changes to the spec--I don't know if any browsers are doing this yet (I've been told Chrome doesn't have it yet).
(Reporter)

Comment 1

5 years ago
It looks like 1015 may be a wart in RFC6455 that we don't actually want to pass up to the JS API, to avoid network sniffing:

  http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0437.html

  http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0437.html

I'm trying to get clarification (and clear language in the W3C spec).  But I suspect this will be WONTFIX
Whiteboard: [necko-would-take]
You need to log in before you can comment on or make changes to this bug.