I set up a SOCKS proxy at port 9090 to computer B elsewhere:
ssh -D localhost:9090 user@B
and configured it in my local Google Chrome browser. However, computer B is behind an HTTP proxy, so HTTP requests originating locally get to computer B through the SOCKS proxy but can't be addressed (terminal running ssh -D localhost:9090 user@B shows "open failed: connect failed: No route to host" when such a request is made).
I have tried:
- setting up BOTH remote HTTP proxy (behind which computer B is) and SOCKS proxy in Google Chrome,
- running ssh -D localhost:9090 user@B with environment variable http_proxy properly set,
- adding http_proxy=_proxy_address_ to the user's .bashrc on computer B;
but none worked.
Anyone knows how to configure the SOCKS proxy so as to take into account the HTTP proxy behind which computer B is? Any method which does not involve changing SSHD or global configuration at the server would be prefered.