Re: many forward socks5

Fabian Keil <[email protected]> Thu, 1 Dec 2022 19:52:16 +0100

Newsgroups	gmane.comp.web.privoxy.user
Message-ID	<[email protected]>

Mike Tkatchouk <[email protected]> wrote on 2022-12-01 at 23:47:28:

> Hi all. I want to use privoxy to work with different socks5 proxies.
> 
> My configuration looks like this:
> 
> forward-socks5 / localhost:9050 .
> forward-socks5 / localhost:9050 .

These two lines look the same?

> forward-socks5 / localhost:9051 .
> forward-socks5 / localhost:9052 .
> forward-socks5 / localhost:9053 .
> forward-socks5 / localhost:9054 .
> 
> Privoxy is part of the squid-privoxy-many sock5 proxy cascade.

Your forward-socks5 directives all have the same URL pattern ("/")
so at the moment the last one is expected to overrule the previous
ones.

It's not entirely clear to me what behaviour you desire.

On our TODO list we have:
|  19) enable-forward-fallback. Syntax? Suggested by K.R.
<https://www.privoxy.org/gitweb/?p=privoxy.git;a=blob;f=TODO;hb=HEAD#l53>

Is that what you want?

I, too, use multiple forwarding proxies but I let Privoxy
chose the forwarding proxy based on the URL and the client
headers.

> For some reason it does not work stably, for different clients. Chrome 
> throws an error: ERR_EMPTY_RESPONSE.
> 
> Naturally, each socks5 proxy is available separately.

To diagnose the Chrome issue it would probable help to
check the Privoxy log after enabling the debug directives
suggested at:
<https://www.privoxy.org/user-manual/contact.html>

Fabian

_______________________________________________
Privoxy-users mailing list
[email protected]
https://lists.privoxy.org/mailman/listinfo/privoxy-users

signature.asc (application/pgp-signature, 833 B)