1305386 - Websockets not responding until I reset start page (!?)

Status: RESOLVED INCOMPLETE

(Core :: Networking: WebSockets, defect)

Description

[Thorsten]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Build ID: 20160922113459

Steps to reproduce:

A) Having a (not public visible) intranet page X as startpage in Firefox.
B) After login to another intranetpage Y, two websockets are opened for realtime notifications. 


Actual results:

Both websockets seem to do their handshake and everything seems fine, but one of them doesn't receive data. It doesn't get a timeout either.

The VERY strange thing happening is: Once I reset Firefox's startpage to default (instead of the other intranet page), everything works as intended. 

I'm quite sure it's not a firewall problem or the anti virus software (I disabled those for tests).

I sadly can't look into the intranet-server Y (third party "black box") and have no clue how this can be connected in any way, but still, I can reliable reproduce the bug by re-activating the old startpage. 

Anybody got a clue how these can be connected?


Expected results:

Websockets should send/receive data.

Comment 1

[Dragana Damjanovic [:dragana]]

Michal, can you please take a look?

Comment 2

[Michal Novotny [:michal]]

I have no idea how this could be related and I cannot do much without reproducible test case.

Thorsten, I have several questions:

1) I assume that by startpage you mean home page. Do you also need to have option "When Firefox starts" set to "Show my home page" to be able to reproduce the problem?

2) Is it reproducible only with a specific home page X or can it be anything non default?

3) Is page X loaded in some other tab when websocket is not responding on page Y?

4) Does page X need to be loaded before the problem can be reproduced? I.e. you can try to run firefox with URL of page Y as a parameter, this starts firefox directly with page Y and no portion of page X will be loaded.

5) Is it reproducible with other websocket page? E.g. try some demos on https://www.websocket.org/demos.html


Could you please provide NSPR log with the failure? To make the logs small and readable, make sure to minimize session duration, i.e. start browser, do only minimum what's needed to reproduce the problem and close the browser. Here is how to create the log https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging. MOZ_LOG_MODULES for this bug should be sync,timestamp,nsHttp:5,nsWebSocket:5