-
Notifications
You must be signed in to change notification settings - Fork 150
Allow for other hosts than localhost to be proxied.
#128
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
Conversation
yuvipanda
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this!
I want to make sure that we only allow people to do this from subclassed hadnlers, and we make it so they explicitly are aware of the risks. I've left some comments, but will think a little more on how to make it harder to accidentally make this exploitable.
meant to be overridden.
|
@ian-r-rose this looks good to me! Unfortunately there are no tests :| Can you do a bunch of local testing to see if it works ok? Would be even better if you can add a quick test or two, but I understand if you don't want this to block on that. |
|
I've tested the I can try to add some tests this evening. |
|
I assume you also have some of extensions which it might be good to check with @yuvipanda? |
|
@ian-r-rose would <3 if you could add some simple tests :) |
|
I've added a very basic test, the great majority of the effort for which went into setting up the serverextension. |
|
Thanks for all the awesome work, @ian-r-rose! <3 |
Finishes the work needed for #70, dask/dask-labextension#58.
This allows the developer to specify a non-localhost URI to be proxied. It should be a non-breaking change for users to
LocalProxyHandler. It seems to work well in my testing, but @yuvipanda and @ryanlovett have a much better idea of the range of places wherejupyter-server-proxyare deployed.