-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebSocket repeated disconnects by using sockjs@0.3.18 #699
Comments
Confirmed that the bug is happening on the latest beta. Will investigate, but all help is welcome. |
Investigated it a bit: this happens only when using http/2. If you'd set |
Hmm this is rather ugly, but it seems Safari doesn't "trust" the certificate used for the WebSocket, even if you click "Continue to untrusted page" when loading the page. This article explains what you have to do to "trust" the certificate. For future reference, here's a tl;dr:
I verified that this fixed the issue. It is not a nice workaround, but unfortunately I see no other way to fix this behavior in webpack-dev-server (without breaking http/2). If anyone knows a better way, please don't hesitate to do a PR or comment here. |
I'm submitting a bug report
webpack and webpack-dev-server version:
webpack: 2.1.0-beta.27
webpack-dev-server: >=2.1.0-beta.7
Please tell us about your environment:
OSX 10.x
Docker / Vagrant
Running server via CLI
Safari version: 10.0.1 (12602.2.14.0.7)
Current behavior:
using CLI
webpack-dev-server -d --progress
with
devServer
config:Expected/desired behavior:
Runnig webpack-dev-server on Safari should work as same as Chrome and Firefox
Current result:
Got
WebSocket network error: OSStatus Error -9807
from SafariWebSocket repeated disconnects.
I investigated a bit different beta version of
webpack-dev-serve
2.0+, it seems like the issue caused bysockjs@0.3.18
to make secure WebSocket via SSL. I downgradewebpack-dev-server
to2.1.0-beta.6
then it works fine.Any reason why after
2.1.0-beta.6
,webpack-dev-server
upgradesockjs
to0.3.18
?The text was updated successfully, but these errors were encountered: