[Privoxy-users] forward-override DNS

[Fabian Keil]

Theo Cushion <mrtheo at gmail.com> wrote:

> 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?

This is not expected. With "forward-override{forward the_parent_proxy:80}"
Privoxy shouldn't attempt to do a DNS lookup either.

Did you enable logging to confirm that the forward-override action
is enabled? A log excerpt would probably help to debug this.

Fabian


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.privoxy.org/pipermail/privoxy-users/attachments/20180314/b5db2f7b/attachment.bin>