Bueno, ya he visto que en el privoxy se puede hacer:
7.5. Forwarding
This feature allows routing of HTTP requests through a chain of multiple proxies. It can be used to better protect privacy and confidentiality when accessing specific domains by routing requests to those domains through an anonymous public proxy (see e.g.
http://www.multiproxy.org/anon_list.htm) Or to use a caching proxy to speed up browsing. Or chaining to a parent proxy may be necessary because the machine that Privoxy runs on has no direct Internet access.
Also specified here are SOCKS proxies. Privoxy supports the SOCKS 4 and SOCKS 4A protocols.
7.5.1. forward
Specifies:
To which parent HTTP proxy specific requests should be routed.
Type of value:
target_pattern http_parent[:port]
where target_pattern is a URL pattern that specifies to which requests (i.e. URLs) this forward rule shall apply. Use / to denote "all URLs". http_parent[:port] is the DNS name or IP address of the parent HTTP proxy through which the requests should be forwarded, optionally followed by its listening port (default: 8080). Use a single dot (.) to denote "no forwarding".
Default value:
Unset
Effect if unset:
Don't use parent HTTP proxies.
Notes:
If http_parent is ".", then requests are not forwarded to another HTTP proxy but are made directly to the web servers.
Multiple lines are OK, they are checked in sequence, and the last match wins.
Examples:
Everything goes to an example anonymizing proxy, except SSL on port 443 (which it doesn't handle):
forward / anon-proxy.example.org:8080
forward :443 .
Everything goes to our example ISP's caching proxy, except for requests to that ISP's sites:
forward / caching-proxy.example-isp.net:8000
forward .example-isp.net .
7.5.2. forward-socks4 and forward-socks4a
Specifies:
Through which SOCKS proxy (and to which parent HTTP proxy) specific requests should be routed.
Type of value:
target_pattern socks_proxy[:port] http_parent[:port]
where target_pattern is a URL pattern that specifies to which requests (i.e. URLs) this forward rule shall apply. Use / to denote "all URLs". http_parent and socks_proxy are IP addresses in dotted decimal notation or valid DNS names (http_parent may be "." to denote "no HTTP forwarding"), and the optional port parameters are TCP ports, i.e. integer values from 1 to 64535
Default value:
Unset
Effect if unset:
Don't use SOCKS proxies.
Notes:
Multiple lines are OK, they are checked in sequence, and the last match wins.
The difference between forward-socks4 and forward-socks4a is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS server, while in SOCKS 4 it happens locally.
If http_parent is ".", then requests are not forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through a SOCKS proxy.
Examples:
From the company example.com, direct connections are made to all "internal" domains, but everything outbound goes through their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to the Internet.
forward-socks4a / socks-gw.example.com:1080 www-cache.example-isp.net:8080
forward .example.com .
A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this:
forward-socks4 / socks-gw.example.com:1080 .
7.5.3. Advanced Forwarding Examples
If you have links to multiple ISPs that provide various special content only to their subscribers, you can configure multiple Privoxies which have connections to the respective ISPs to act as forwarders to each other, so that your users can see the internal content of all ISPs.
Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to isp-b.net. Both run Privoxy. Their forwarding configuration can look like this:
host-a:
forward / .
forward .isp-b.net host-b:8118
host-b:
forward / .
forward .isp-a.net host-a:8118
Now, your users can set their browser's proxy to use either host-a or host-b and be able to browse the internal content of both isp-a and isp-b.
If you intend to chain Privoxy and squid locally, then chain as browser -> squid -> privoxy is the recommended way.
Assuming that Privoxy and squid run on the same box, your squid configuration could then look like this:
# Define Privoxy as parent proxy (without ICP)
cache_peer 127.0.0.1 parent 8118 7 no-query
# Define ACL for protocol FTP
acl ftp proto FTP
# Do not forward FTP requests to Privoxy
always_direct allow ftp
# Forward all the rest to Privoxy
never_direct allow all
You would then need to change your browser's proxy settings to squid's address and port. Squid normally uses port 3128. If unsure consult http_port in squid.conf.
You could just as well decide to only forward requests for Windows executables through a virus-scanning parent proxy, say, on antivir.example.com, port 8010:
forward / .
forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010
Ahora me falta digerirlo, y editar el archivo de configuracion(eso tambien tengo que ver cual es, porque tiene 4.) :lol:
