Certain sites must be accessed through a SOCKS server
All other sites must be accessed though a http proxy, except a few wich
must be accessed directly.
I have tried to do this with a proxy.pac file, but I couldn't get it to work; no matter what I did, Firefox never did DNS through the SOCKS server. FoxyProxy seemed to be the answer to all my problems (and it was, almost)
In my configuration I have:
*asite/* (Wildcard, whiteliste)
http?://.*\.our\.domain/.* (RegExp, whitelist)
"Use SOCKS proxy for DNS lookups" is enabled.
If I access http://asite.our.domain
the request is routed through the SOCKS proxy (according to the log) and the page loads.
If I access http://asite
the request is routed through the SOCKS proxy(according to the log) but all I get is a blank page (and nothing show up in the server's log)
Any ideas? (and just using the domain is not an option as some sites are developed by stupid people who use http://<site>/blah.html in links).
Firstly, if you have a PAC file already written which does what you want, you can use the PAC file in FoxyProxy and still configure FoxyProxy to use a SOCKS server for DNS lookup. However, if the PAC file sometimes specifies a non-SOCKS proxy and you want those URLs to be resolved through the SOCKS proxy (but loaded through an HTTP proxy), that could be a problem... I haven't tried that.
The second rule,
http?://.*\.our\.domain/.* (RegExp, whitelist), doesn't seem to apply here so I'll ignore it unless you tell me otherwise. The first rule looks ok, although I'm tempted to refine it a little more; e.g., *://asite.???/*. In any case, what happens if you load this URL without FoxyProxy; i.e., with FoxyProxy disabled and Firefox configured to use the SOCKS proxy. Do you also get a blank page?