Skip to content
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

live stream fails with ws close: 1006 on URLs with port numbers #219

Closed
scottlamb opened this issue Apr 14, 2022 · 0 comments
Closed

live stream fails with ws close: 1006 on URLs with port numbers #219

scottlamb opened this issue Apr 14, 2022 · 0 comments

Comments

@scottlamb
Copy link
Owner

As mentioned in #218 (comment), there's a problem with my 0.7.3 security fix (changelog entry, commit). If the browser URL has a port number (including the out-of-the-box instructions to use port 8080), the live stream will never authenticate properly. Rather than the server accepting the websocket upgrade, it will send back a HTTP 403 with a body like this:

Permission denied: cross-origin request forbidden (request host "slamb-workstation:8080", origin host "slamb-workstation")

...which the browser UI won't show. It'll just give the classic ws close: 1006 error.

scottlamb added a commit that referenced this issue Feb 16, 2023
This gives much better information to the UI layer, getting rid of a
whole troubleshooting guide entry. See #119 #132 #218 #219

I also restructured the code in anticipation of a new WebSocket event
stream (#40).
scottlamb added a commit that referenced this issue Feb 16, 2023
This gives much better information to the UI layer, getting rid of a
whole troubleshooting guide entry. See #119 #132 #218 #219

I also restructured the code in anticipation of a new WebSocket event
stream (#40).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant