[Privoxy-users] forward-override DNS
Theo Cushion
mrtheo at gmail.com
Tue Mar 13 15:38:35 UTC 2018
Hi,
I have several several proxy servers that are used to access various different services. Some of these require authentication while others do not.
Reading through the documentation it looks like I should use actions to ensure that the Proxy-Authorization header is added, and I can use forward-override to go to the correct proxy server.
My example user.action is this:
{{alias}}
authenticated-proxy = +add-header{Proxy-Authorization: Basic <BASE64 User password>} +forward-override{forward the_parent_proxy:80}
unauthenticated-proxy = +forward-override{forward another_parent_proxy:80}
{ authenticated-proxy }
/
My config file is pretty standard.
I’ve used config.privoxy.org <http://config.privoxy.org/> to check that the URL’s I’m interested in have the correct actions applied - they do. However, when making a request I get a 404 response because the DNS cannot be resolved (my local machine cannot resolve DNS and relies on the proxies to do this)
However, if I remove the forward-override in the user.action stuff and in config.txt just do:
forward / the_parent_proxy:80
Then Privoxy appears to use the parent proxy to resolve the requests as expected and it all works. Looking through the manual I can’t see any settings that look like they affect this behaviour? Is this expected?
I’m trying to avoid having some URL patterns in the user.action and some in the main config as I do not want to get into a situation whereby if they differ in those 2 locations then I start sending credentials to the wrong server.
Is it possible to use forward-override to resolve DNS without using a socks forwarder? If not, is there a way of guaranteeing that the rules for forward and the rules for adding headers are always the same (when spread between config.txt and user.action)?
Any help would be greatly appreciated.
Thanks,
Theo
More information about the Privoxy-users
mailing list