WebSocket is closed before the connection is established

[shinigami1992]

Hi guys, thank you for your awesome library.

I've used sockjs-client for connecting my web app to a spring websocket web server, the problem is that when i refresh related browser page, sometimes (about 5%) this error will happen.

WebSocket connection to 'ws://localhost:4568/ws/379/lsb17jhg/websocket?X....' failed: WebSocket is closed before the connection is established

maybe useful to say that I didnt call disconnect or close anywhere in my code.

Thank you.

[brycekahle]

What browser? Was the WebSocket connected when you refreshed? If not, this could just be a browser warning.

[Southpaw17]

Have you tried ending the socket connection before refreshing the page? There is a similar issue to this on the Primus Issue Tracker: primus/primus#398

The suggested workaround there is to do the following:

window.addEventListener("beforeunload", function (event) { primus.end(); });

[shinigami1992]

@brycekahle Google Chrome on OSX. Yeah when i refresh the page, it will connect.

@Southpaw17 Thanks for your hint. What's equivalent code in sockjs-client? Should I use Primus library to overcome this issue?

Thanks.

[brycekahle]

@majeedsan It does appear we will close the websocket on unload without ensuring that the open event has fired.

sockjs-client/lib/transport/websocket.js

Lines 43 to 46 in 4027289

	this.unloadRef = utils.unloadAdd(function() {
	debug('unload');
	self.ws.close();
	});

[brycekahle]

Unfortunately we don't have any other way to stop the websocket from continuing the connection attempt (other than relying on the browser to stop it) on page unload. I think it is safe to ignore the browser warning. What do you think?

[ryanbrandenburg]

We have the same problem (though through a couple layers of indirection because we're seeing it from angular webpack) but it happens 100% of the time.

Repro steps:

1. Install a 3.0 preview of dotnet.
2. dotnet new angular
3. dotnet run from within the new template.
4. Visit the page and check the console to view the warning (error on Firefox).

[github-actions]

This issue has been inactive for 30 days. It will be in closed in 5 days without any new activity.