[squid-users] Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: [squid-users] Re: Antwort: Re: [squid-users] Question to cache_peer

babajaga <augustus_meyer_at_yahoo.de> schrieb am 04.07.2014 11:54:04:

> Von: babajaga <augustus_meyer_at_yahoo.de>
> An: squid-users_at_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-tp4666616p4666646.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
[email protected], http://www.mahle.com
Received on Fri Jul 04 2014 - 12:13:19 MDT