1619520 - Abrupt Websocket disconnect

Status: RESOLVED INVALID

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

Description

[samofoz]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.122 Safari/537.36

Steps to reproduce:

Firefox 73.0.1 (64-bit)
Simply connect a websocket from javascript to a websocket server. The websocket server sends a buffer of size 16500 bytes or more upon connect or later.

Actual results:

Following is printed on the javascript console:

The connection to wss://localhost:80/ was interrupted while the page was loading
Websocket error (callback) with code:undefined reason:undefined
Websocket closed (callback) with code:1006 reason:

Expected results:

Connection should not have been interrupted.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[Dragana Damjanovic [:dragana]]

Michal, can you take a look? Is this something we already know about, it sounds familiar or we have fixed a similar issue?
Adjust priority as you see fit.

Comment 3

[Michal Novotny [:michal]]

Could you please provide a log? See https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging and please add nsWebSocket:5 to the list of logged modules.

Comment 4

[samofoz]

Attachment: log.txt-main.12504.zip

Logs attached

Comment 5

[samofoz]

Attachment: log.txt-child.14284.zip

Logs with websockets attached.

Comment 6

[samofoz]

Hi team, are you guys looking into this?Thanks.

Comment 7

[Michal Novotny [:michal]]

Could you please test whether you see the problem if you don't use WS over HTTP/2? Also could you please provide a test case so I can test it locally?

Comment 8

[samofoz]

Message fragmentation seems to have solved the problem:
https://tools.ietf.org/html/rfc6455#section-5.4