Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • cool, I can try the other loopback addresses. Could you add an example of using unix sockets as well? just curious how it would work. Commented Mar 30, 2020 at 17:41
  • I don't know if the servers are programmed to do it. But you could listen on a high port, and use port forwarding. I just went for multiple loop-back addresses. Commented Mar 30, 2020 at 19:49
  • yeah the multiple loop back addresses is cool. will prob use that. but I am really curious how it could be done with unix domain sockets, any idea how? Commented Mar 30, 2020 at 22:47
  • 1
    I would look at netcat. It may be able to forward it. ssh can do it but there is overhead of encryption. Both would need the server to listen on a socket, and would just forward from another unix socket. I think I did it once. But could not convince the browser to use it. I would ask another question. But be clear about what you are not asking for, and link to this question. Commented Mar 31, 2020 at 19:18
  • 1
    yeah but netcat would be listening on a port and then forwarding to the unix domain socket? ultimately I am trying to avoid listening on a port at all, so that defeats the purpose, but your original idea to use a different loopback address is good. Commented Mar 31, 2020 at 19:36