-
-
Notifications
You must be signed in to change notification settings - Fork 488
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 Connection blocked when serving over HTTPS #195
Comments
You're right about that. Do you have an idea of how complicated it would be to support secure web sockets from the node server side? Or, as the connection likely won't succeed anyway as you're not probably running a watcher when serving over HTTPS, should we just not try opening the websocket connection in the first place is page is served over HTTPS? |
I don't know much about Secure WebSocket in Node. My case would be solved if I could either
As a side note, why an option to disable it would be good: |
I just run into the same problem in Jenkins. I'm using webpack-bundle-analyzer in static mode and publishing the report.html using he Jenkins publishHtml plugins. I agree that disabling websockets in static mode, makes a lot of sense. The report displays (after relaxing Jenkins CSP settings) but would be nice to silence the error. |
If either one of you feels like taking a stab at this, we'd be happy to review a PR |
The opened WebSocket connection is always
ws:
. If the file is served via HTTPS, this should bewss:
or else the browser will block the connection.Message from Chrome:
The culprit is here, probably:
webpack-bundle-analyzer/client/viewer.jsx
Line 11 in 2c05555
The text was updated successfully, but these errors were encountered: