1071708 - WebSocket onclose not called when using wss://

Status: UNCONFIRMED

(Core :: Networking: WebSockets, defect, P3)

Description

[Iñaki Baz Castillo]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.122 Safari/537.36

Steps to reproduce:

1) Open any web in which a WSS connection is feasible, and open the JS console.

2) Let's assume the URI is:  var uri = "wss://example.com".

3) In the console (in the same line):

  ws = new WebSocket(uri);  ws.onopen = function(e) { console.warn("ws.onopen() !!!"); };  ws.onclose = function(e) { console.warn("ws.onclose() !!!"); };

4) Ensure the onopen callback is called.

5) Call ws.close().


The same bug also happens in Chrome 37.0.2062.122 and  39.0.2166.2 canary (64-bit) in OSX:

https://code.google.com/p/chromium/issues/detail?id=93698#c15


Now repeat the same steps with a ws:// URI. The onclose is called.


Actual results:

onclose is NOT called.


Expected results:

onclose callback should be called.

Now repeat the same test with a ws:// URI. onclose will be called.

Comment 1

[Iñaki Baz Castillo]

I'm sorry, the issue reported in Chrome is this one:

https://code.google.com/p/chromium/issues/detail?id=388243

Note that they have recently fixed it.

Comment 2

[Nikhil Marathe [:nsm] (No longer reading bugmail, please needinfo?)]

(In reply to Iñaki Baz Castillo from comment #1)
> I'm sorry, the issue reported in Chrome is this one:
> 
> https://code.google.com/p/chromium/issues/detail?id=388243
> 
> Note that they have recently fixed it.

It was marked WontFix. Are you referring to the bug in the original description?

Comment 3

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 4

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258