using a server worker as a forward proxy

[GitHub4LP]

Proposed change

Some service responses are based on the root path, but the actual address that can be accessed is based on the subpath /jupyter_subpath/proxy/{{port}}/, can there be a solution to solve this kind of problem, e.g., using a server worker as a forward proxy?

Alternative options

Optional

Who would use this feature?

Some service responses are based on the root path, but the actual address that can be accessed is based on the subpath /jupyter_subpath/proxy/{{port}}/

(Optional): Suggest a solution

server worker as a forward proxy

[manics]

Jupyter-server-proxy already has absolute_url and mappath options, is there anything that can't be handled by these?

[GitHub4LP]

Jupyter-server-proxy already has absolute_url and mappath options, is there anything that can't be handled by these?

Some web services respond based on /, i.e., the browser automatically requests host/x , but through the jupyter-server-proxy, the real address can be accessed is host/jupyter_subpath/proxy/{{port}}/x , through the server worker can intercept the host/x, and instead request the host/jupyter_subpath/proxy/{{port}}/x response
@manics

[manics]

Unfortunately that's not possible. Jupyter Server only has control of paths under http://host/jupyter_subpath/. If you want control of paths outside of jupyter-server (i.e. http://host/x you'll probably need to use a front-end proxy (e.g. nginx, traefik, etc) with a custom route

[GitHub4LP]

I mean, a server worker can do that.
@manics