I’m making some assumptions here, and if they’re not true, you can either 
correct me, or if the functionality i describe is what you want, take a look at 
https://www.cryptomonkeys.com/2014/07/automatic-http-proxy/ where I detail how 
to set this up.

Presumably you have:
a) a web server that is passing the proxy.pac file out, and generating logs
b) configured the browser’s proxy settings to “auto”

When you start/load the browser, you should be able to see in the webserver’s 
logs that its pulling a copy of the proxy.pac file. If this isn’t the case, 
that’s likely to be your problem. The site you mention is a little light on 
details for all this, so I’m not sure if you only have a partial setup, or if 
you’ve misconfigured something.


> On Feb 24, 2016, at 8:45 PM, Robert Citek <[email protected]> wrote:
> 
> Greetings all,
> 
> I have created a SOCKS proxy on a remote server that listens on port
> :5150 and have manually configured my browsers (Chrome, Firefox) to
> use it.
> 
> As the next step, I would like to create a proxy.pac file to
> automatically configure my web browsers to use the SOCKS proxy.  I
> have created a proxy.pac file similar to the one on this page:
> 
> https://mikewest.org/2007/01/auto-configuring-proxy-settings-with-a-pac-file
> 
> which looks like this:
> 
> function FindProxyForURL(url, host) {
>  return "SOCKS 10.1.2.10:5150";
> }
> 
> It seems to work.  Except, that when I change the proxy port on the
> remote from :5150 to :5151, my browser still is able to connect to
> remote sites.
> 
> I have a number of questions, but foremost is, how can I tell if the
> browser is using the proxy or not?
> 
> Regards,
> - Robert
> _______________________________________________
> PLUG mailing list
> [email protected]
> http://lists.pdxlinux.org/mailman/listinfo/plug

--
Louis Kowolowski                                [email protected] 
<mailto:[email protected]>
Cryptomonkeys:                                   http://www.cryptomonkeys.com/ 
<http://www.cryptomonkeys.com/>

Making life more interesting for people since 1977

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to