[Webkit-unassigned] [Bug 81072] [WebSocket]Browser should use 1000 as status code when WebSocket API close is called without status code parameter.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=81072





--- Comment #7 from Li Yin <li.yin at intel.com>  2012-04-22 01:14:07 PST ---
(In reply to comment #6)
> Hi joey, thank you for a patch.
> Originally, I implemented this WebSocket::close method for new hybi/rfc protocol.
> 
> Before hybi-06, the WebSocket protocol didn't have the status code and the reason. At that time, the WebSocket API doesn't allow any argument for close method.
> From the viewpoint of protocol and API history, I decided to send close frame with empty body when user call close without any argument.

>From the bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=16703
It still have no obvious definition about the default status code in the spec, but it seems that 1000 should be.
Do you think it is necessary to use 1000 instead of no status code?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.