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
Websocket requests are not mapped via mappath. The function is not even called on the websocket URL.
How to reproduce
Write a small server proxy that contains a websocket request, use the mappath config argument to define a function that e.g. just prints and returns the current path. It is not called for the websocket request, the console shows
Trying to establish websocket connection to ws://...
Websocket connection established to ws://...
where ws://... is the original path, not mapped using mappath.
Expected behaviour
ws://... should be a path mapped using the custom mappath function.
Actual behaviour
ws://... is the original, unmapped path.
Your personal set up
OS: Fedora Workstation 41
Version(s): Jupyter Server Proxy version 4.4.0
The text was updated successfully, but these errors were encountered:
This is done by instead of WebSocketHandlerMixin providing the default `get` method and delegating to `ProxyHandler.http_get`, it now provides `get_websocket` and `ProxyHandler.proxy` delegates to it.
Code is also removed that was never reached since it checked for the "Upgrade" HTTP header after removing it among others defined in `hop_by_hop_headers`.
Fixesjupyterhub#525
2xB
linked a pull request
Apr 13, 2025
that will
close
this issue
Bug description
Websocket requests are not mapped via
mappath
. The function is not even called on the websocket URL.How to reproduce
Write a small server proxy that contains a websocket request, use the
mappath
config argument to define a function that e.g. just prints and returns the current path. It is not called for the websocket request, the console showswhere
ws://...
is the original path, not mapped usingmappath
.Expected behaviour
ws://...
should be a path mapped using the custommappath
function.Actual behaviour
ws://...
is the original, unmapped path.Your personal set up
The text was updated successfully, but these errors were encountered: