Skip to content

Commit ac76d02

Browse files
authored
Remove mention of unix socket since it's an open PR.
1 parent 6df5c7f commit ac76d02

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

README.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ contains information on installation & usage.
3535
## Security warning
3636

3737
Jupyter Server Proxy is often used to start a user defined process listening to
38-
some network port (http://localhost:4567) for a user starting a Jupyter Server
38+
some network port (e.g. http://localhost:4567) for a user starting a Jupyter Server
3939
that only that user has permission to access. The user can then access the
4040
started process proxied through the Jupyter Server.
4141

@@ -45,9 +45,7 @@ the Jupyter Server's authorization!
4545

4646
A common strategy to enforce access proxied via Jupyter Server is to start
4747
Jupyter Server within a container and only allow network access to the Jupyter
48-
Server through to the container. Another strategy is to communicate with the
49-
started process through a unix socket as proposed in [Pull request
50-
#337](https://github.com/jupyterhub/jupyter-server-proxy/pull/337).
48+
Server via the container.
5149

5250
For more insights, see [Ryan Lovetts comment about
5351
it](https://github.com/jupyterhub/jupyter-server-proxy/pull/359#issuecomment-1350118197).

0 commit comments

Comments
 (0)