You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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).
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).
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:
...which the browser UI won't show. It'll just give the classic
ws close: 1006
error.The text was updated successfully, but these errors were encountered: