Open
Bug 1192232
Opened 10 years ago
Updated 3 years ago
Websocket is closed with code 1006 once it receives message from server
Categories
(Core :: Networking: WebSockets, defect, P3)
Tracking
()
UNCONFIRMED
People
(Reporter: yuliya.ivaniukovich, Unassigned)
Details
(Whiteboard: [necko-backlog])
Attachments
(1 file)
|
36.14 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.125 Safari/537.36
Steps to reproduce:
I have a simple WebSocket server written using https://github.com/sta/websocket-sharp library.
I've connected to it using simple code:
var socket = new WebSocket("ws://localhost:8081");
socket.onerror = function(event) {
console.log("WS error: ");
console.log(event);
};
socket.onclose = function(event) {
console.log("WS close: ");
console.log(event);
};
socket.onmessage = function (event) {
console.log(event.data);
}
Then I tell the server to send a message to the client
Actual results:
Once the first message form the server is received connection is closed with code 1006 due to some error (caught by onerror handler). Neither error nor close event has any details about what has happened. See attachment for console output.
PS: see also the last comment from Fabio Melo in the bug report https://bugzilla.mozilla.org/show_bug.cgi?id=712329
I believe he is referring to the same issue
Expected results:
In version 36 there is no such issue, connection stays alive and continue receiving messages (same works in Chrome and IE).
I expect to see the same in newer versions. Or at least some reason message about what has happened.
Updated•10 years ago
|
Component: Untriaged → Networking: WebSockets
Product: Firefox → Core
Updated•10 years ago
|
Whiteboard: [necko-backlog]
Comment 1•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Comment 2•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•