Nw.js: WebSocket not working on spotify.com

[Virius]

NWJS Version : v0.29.1
Operating System : Win10 x64

Expected behavior

new WebSocket(address) work ok

Actual behavior

new WebSocket(address) produce error "WebSocket connection to 'wss://gew-dealer.spotify.com/?access_token=...' failed: Error in connection establishment: net::ERR_NOT_IMPLEMENTED"

How to reproduce

• open nw.js dev console
• execute window.location.href = 'https://open.spotify.com'
• log in to site

In console logs you will see net::ERR_NOT_IMPLEMENTED errors

Another way:

• open nw.js dev console
• execute window.location.href = 'https://open.spotify.com'
• execute new WebSocket('wss://gew-dealer.spotify.com');

will generate same error.

In Chrome all works fine. And if I start Fiddler on my computer then in nw.js all works fine too. Can anybody explain why?

[Christywl]

I can reproduce this issue on Linux/Windows with nwjs-sdk-v0.29.1.

[rogerwang]

This looks like https://bugs.chromium.org/p/chromium/issues/detail?id=684681 .
Will check why it works fine in Chrome. Maybe it connects to a different server or using different protocol.

[rogerwang]

Ref: https://github.com/nghttp2/nghttp2/issues/793

[rogerwang]

I can reproduce this with the latest Chromium (not chrome): https://download-chromium.appspot.com/dl/Linux_x64

So should be an upstream issue.

[rogerwang]

@Virius please report your findings to upstream. Thanks. https://crbug.com/new

[Virius]

@rogerwang Created. https://bugs.chromium.org/p/chromium/issues/detail?id=823643

[Virius]

Hi. Chromium developers saу that the problem is not on their side (https://bugs.chromium.org/p/chromium/issues/detail?id=823643). Can you check nw.js again? May be need specify some additional arguments to gn build process. Or can tell me what to answer the developers of chromium?

[rogerwang]

I just followed up in the upstream issue. btw, you should use the link https://download-chromium.appspot.com/dl/Linux_x64 which is official binary.

[Virius]

Hi. Can you explain the last comment in chromium issue discussion (https://bugs.chromium.org/p/chromium/issues/detail?id=823643#c21). I do not understand, the problem is solved? In which chromium release? When this changes will be in the nw.js?

[rogerwang]

It's in chrome 67 / nwjs 0.31. Will look to backport it to 0.30.

[rogerwang]

This is backported and fixed in git. It will be available in the next nightly build.