Re: Web tunnelling/static IP
- From: David Sankey <David.Sankey@xxxxxxxxxx>
- Date: Thu, 18 Dec 2008 16:26:42 +0000
In article <v23o16-8i2.ln1@xxxxxxxx>, rpg@xxxxxxxxxxxxx (rpg) wrote:
David Sankey <David.Sankey@xxxxxxxxxx> wrote:
The first article has a sensible description of setting up a socks proxy
over ssh, but then describes a rather strange way of configuring Firefox
to use it.
A less convoluted way is to use your own proxy.pac file which contains
at least the following:
function FindProxyForURL(url, host) {
return "SOCKS localhost:8080; DIRECT";
}
The 8080 is the (local) port at which your web browser finds its socks
proxy.
That still only works for https addresses though.
*seriously* confused. How do I slurp http: over SOCKS?
You don't need to know - it's the browser that knows how to route over a
socks proxy.
I'm not entirely sure what you're doing wrong, as I routinely use this
method to route http over socks, details as follows.
Unless this is a mismatch between localhost and 127.0.0.1, as I recall
the ssh example used the latter?
Or maybe the 8080 causes difficulty. The socks port is normally 1080
albeit this shouldn't matter (I use ports 1080 and 2080 for the two
sites).
I have the ssh chicanery defined in my .ssh/config:
Host *.where.ever
DynamicForward localhost:1080
And in my proxy.pac I route just http (I found that safari baulks at
routing https over a socks proxy, firefox is OK, but I don't know how to
distinguish between the two in the proxy.pac file):
else if (dnsDomainIs(host, "where.ever")) return "SOCKS
localhost:1080; "+secondary;
But this certainly works (and for the other site on 2080).
Email is correct if you want to pursue this further.
Kind regards,
Dave
.
- References:
- Re: Web tunnelling/static IP
- From: Andrew Collier
- Re: Web tunnelling/static IP
- From: David Sankey
- Re: Web tunnelling/static IP
- Prev by Date: Re: Delivery dates
- Next by Date: Re: Delivery dates
- Previous by thread: Re: Web tunnelling/static IP
- Next by thread: Dirty pea?
- Index(es):
Relevant Pages
|