From: Mike. <the...@mg...> - 2011-06-04 17:33:28
|
On 6/3/2011 at 3:16 PM Harry Putnam wrote: |[snip] | |Chaining in this direction: | Browser -> Squid -> Privoxy -> Privoxy's IP -> Public Internet | ============= As a suggestion, I would chain like: Browser -> Privoxy -> Squid -> external internet The reason: With the chain as you do it, I found that after I would add a new ad blocking URL to privoxy, squid would still have the ad in its cache, and I'd still see the ad. I used the default configuration of squid, except changing the ACL's to allow access needed for privoxy. The salient items forming the processing chain: privoxy's config: listen-address 10.23.90.3:8118 forward / 127.0.0.1:3128 squid's config: http_port 3128 Both squid and privoxy run on a freebsd 8.1 server on my network. All the browsers on the network point to 10.23.90.3:8118 as their proxy. Privoxy does its thing, then forwards the request to squid. All the browsers are configured to clear their cache on exit. Speed is excellent. The network is gigabit ethernet. If the page is cached in squid, the page literally flashes up when I click on the URL. So I would say that you should not see a "massive slowdown when chaining squid => privoxy". |