[Privoxy-users] Unable to forward specific domains through a upstream proxy

[Andrew Rossiter]

fantastic that does it.  and also that explains the logging as i'm using a
docker container version so I guess that falls under that banner.

now to work out how to get all user devices on the network to use the proxy
:-)

thanks
Andrew

On Mon, 25 Nov 2024 at 13:37, Fabian Keil <fk at fabiankeil.de> wrote:

> Andrew Rossiter via Privoxy-users <privoxy-users at lists.privoxy.org> wrote
> on 2024-11-24 at 12:37:37:
>
> > I've been struggling for days now trying to get my privoxy to do the
> > following.   From what I can tell it should be possible (but its not
> > working)
> >
> > - Any traffic destined to a specific url (preferably wildcarded) for
> > example *.google.com to use upstream Socks5 proxy.
> > - All other traffic to go directly (from the privoxy)
> >
> > I've tried so many variations now, with the below attempts, but it is
> only
> > ever sending everything directly.
> [...]
> > forward-socks5 .whatsmyip.org 192.168.0.2:1080 .
> > forward / .
>
> The last match wins so try:
>
> forward / .
> forward-socks5 .whatsmyip.org 192.168.0.2:1080 .
>
> > Note that if i tell it to send ALL traffic via the upstream socks proxy,
> > then it works fine and as expected.   So it seems like it must be the way
> > that privoxy is processing the config/domains.
> > Unfortunately the logging isn't working either , despite having the
> > following in the config, no file gets created
> >
> > logdir /etc/privoxy
> > logfile privoxy.log
>
> You'll additionally need the debug directive:
> https://www.privoxy.org/user-manual/config.html#DEBUG
>
> Note that if Privoxy is started with the --no-daemon option
> it logs to the controlling tty ignoring the logfile directive.
> This is commonly done on GNU/Linux systems using systemd.
>
> Fabian
>