[Webkit-unassigned] [Bug 81072] [WebSocket]Browser should send close frame 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 #5 from joey <li.yin at intel.com>  2012-03-13 23:35:30 PST ---
(In reply to comment #0)
> When WebSocket API close was called like this "ws.cloes()", chromium didn't send the close frame to WebSocket server.
> And WebSocket server still sent frame to browser unexpectedly, it didn't produce some error, but maybe it's not friendly.
> 

I'm sorry for my previous misleading.
>From the newest code, chromium indeed sent close frame, when the close api was called without parameter. 
but it just had no body(status code and reason), which seemed to be allowed by RFC6455.

> Firefox used the status 1000 as the default value, when the close api had no the parameter.

The only difference is that Firefox used normal closure as the default value.

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