- From: <bugzilla@jessica.w3.org>
- Date: Mon, 23 Apr 2012 05:25:31 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16703
Takashi Toyoshima <toyoshim@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |toyoshim@chromium.org
--- Comment #2 from Takashi Toyoshima <toyoshim@chromium.org> 2012-04-23 05:25:29 UTC ---
Hi, I implemented RFC version of WebSocket::close() for WebKit.
Actually, Chrome never send 1005 as a status code.
When user omit close status code and reason, Chrome send a close frame without
any body data. It means the close frame doesn't have any code and reason field.
As Bronislav said, 1005 is a pseudo code for the API layer to represent that
underlaying framing doesn't contains status code. I guess the contributor see
the code as a pseudo code in a server.
AFAIK, close code is not mandatory field for close frames because WebSocket API
allow to omit them.
[from RFC6455 7.1.5.]
> a Close control frame may contain a status code indicating a reason for closure.
> (snip)
> If this Close control frame contains no status code, _The WebSocket
> Connection Close Code_ is considered to be 1005. If _The WebSocket
> Connection is Closed_ and no Close control frame was received by the
> endpoint (such as could occur if the underlying transport connection
> is lost), _The WebSocket Connection Close Code_ is considered to be
> 1006.
I understand this section say that 1005 doesn't mean any error case. It just
means a pear going to close the connection without a code and reason. This is a
case of expected behaviors.
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 23 April 2012 05:25:37 UTC