[Webkit-unassigned] [Bug 81072] New: [WebSocket]Browser should send close frame when WebSocket API close is called without status code parameter.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Mar 13 20:26:56 PDT 2012


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

           Summary: [WebSocket]Browser should send close frame when
                    WebSocket API close is called without status code
                    parameter.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: li.yin at intel.com


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.

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

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



More information about the webkit-unassigned mailing list