[squid-users] Re: Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: Re: [squid-users] Question to cache_peer
So the behaviour you are seeing looks more like a bug in always_direct processing. Which might be specific to the squid version OR the squid.conf in use. I have several squids of different versions with cache_peer in production. The config needs to be different: 2.7: hierarchy_stoplist cgi-bin ? always_direct deny fwd_youtube #So it might depend upon usage/type of ACL never_direct allow fwd_youtube #Needs both 3.3.11: hierarchy_stoplist cgi-bin ? never_direct allow all is sufficient. 3.4.5: hierarchy_stoplist cgi-bin ? never_direct allow all sufficient Willing to do some more research on this one in case of getting some instructions what to look at (special debug ?) -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Question-to-cache-peer-tp416p464.html Sent from the Squid - Users mailing list archive at Nabble.com.
[squid-users] Re: Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: Re: [squid-users] Question to cache_peer
So squid is exactly doing, what you are asking for: cache_peer = local=0.0.0.0 remote=194.99.121.200:3128 flags=1 But probably, this is not what you want, as it is the public IP on the web, the request is forwarded to. So you most likely should use an internal/local IP of your peer here, OR there is a problem with your routing. BTW: babajaga is a Russian witch. Sort of. -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Question-to-cache-peer-tp416p446.html Sent from the Squid - Users mailing list archive at Nabble.com.
[squid-users] Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: Re: [squid-users] Question to cache_peer
babajaga augustus_me...@yahoo.de schrieb am 04.07.2014 11:54:04: Von: babajaga augustus_me...@yahoo.de An: squid-users@squid-cache.org Datum: 04.07.2014 11:55 Betreff: [squid-users] Re: Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: Re: [squid-users] Question to cache_peer So squid is exactly doing, what you are asking for: cache_peer = local=0.0.0.0 remote=194.99.121.200:3128 flags=1 But probably, this is not what you want, as it is the public IP on the web, the request is forwarded to. So you most likely should use an internal/local IP of your peer here, OR there is a problem with your routing. BTW: babajaga is a Russian witch. Sort of. -- View this message in context: http://squid-web-proxy-cache. 1019090.n4.nabble.com/Question-to-cache-peer-tp416p446.html Sent from the Squid - Users mailing list archive at Nabble.com. Hi babajaga the answer to my problem is: always_direct deny all never_direct allow all So, now all traffic is forwarded to the parent. Thank you for your help !! Mit freundlichen Grüßen / Kind regards Mr. Andreas Reschke andreas.resc...@mahle.com, http://www.mahle.com
Re: [squid-users] Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: Re: [squid-users] Question to cache_peer
On 2014-07-05 00:12, andreas.resc...@mahle.com wrote: Hi babajaga the answer to my problem is: always_direct deny all never_direct allow all Also remove hierarchy_stoplist Amos
Re: [squid-users] Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: Re: [squid-users] Question to cache_peer
Hi Amos, Should the wiki article http://wiki.squid-cache.org/Features/CacheHierarchy be updated so that the never_direct allow all is preceded by always_direct deny all? Regards HASSAN On Fri, Jul 4, 2014 at 6:47 PM, Amos Jeffries squ...@treenet.co.nz wrote: On 2014-07-05 00:12, andreas.resc...@mahle.com wrote: Hi babajaga the answer to my problem is: always_direct deny all never_direct allow all Also remove hierarchy_stoplist Amos
Re: [squid-users] Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: Re: [squid-users] Question to cache_peer
On 2014-07-05 00:56, Nyamul Hassan wrote: Hi Amos, Should the wiki article http://wiki.squid-cache.org/Features/CacheHierarchy be updated so that the never_direct allow all is preceded by always_direct deny all? The default for always_direct is to drop through and obey never_direct. There may be a bug in your particular version if you need to set always_direct at all. You do need to remove hierarchical_stoplist and correctly set nonheirarchical_direct though. The wiki page is not quite making that clear. They should result in errors with never_direct deny all rather than going direct though. So the behaviour you are seeing looks more like a bug in always_direct processing. Amos Regards HASSAN On Fri, Jul 4, 2014 at 6:47 PM, Amos Jeffries squ...@treenet.co.nz wrote: On 2014-07-05 00:12, andreas.resc...@mahle.com wrote: Hi babajaga the answer to my problem is: always_direct deny all never_direct allow all Also remove hierarchy_stoplist Amos