forked from jupyterhub/jupyter-remote-desktop-proxy
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
7eb2c50
commit 4b20d1f
Showing
5 changed files
with
72 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
Findings: | ||
- Listens to either localhost or public by default | ||
- Different flags needs to be used | ||
- Tiger's default from local can be changed with "-localhost no --I-KNOW-THIS-IS-INSECURE" | ||
- Turbo's default from public can be changed with "-localhost" | ||
- Connecting from inside a container is to connect from 127.0.0.1, but outside | ||
is to connect from 172 at least on my computer's docker network, which means | ||
that we can be influenced by this when testing. | ||
- When websockify is involved, it becomes complicated to either connect from | ||
within or outside an container. I don't understand the details yet, but it | ||
seems that configuring what it listens to has an impact to pass inside and/or | ||
outside. | ||
- Connecting via jupyter-server-proxy often require a second attempt, likely due | ||
to https://github.com/jupyterhub/jupyter-server-proxy/issues/459 and letting a | ||
websocket handshake finalize before its finalized against the proxied backend. |