RE: Questionaire 'bout cache_peer_access

Hello,there.

Thank you for your prompt reply > Henrik

My problem with cache_peer_access has NOT solved yet.
Exactly speaking, after additional configuration it was solved,
but another problem has occuered... T_T

Via cache_peer_access configuration, cache_peer_domain
configuration has been canceled. Not effective.
Please let me clarify the procedure of change.

[ Step1 ]

I referred your advice shown as below and set it as the desciption of
that part. ( I mean http_access deny for net5 !all )
It looked that acted nothing...

   Before : http_access allow net5
   After : http_access deny net5 !all

In my articles> combining acl configuration and cache_peer_access
> it resulted in failure.
> acl net5 dst 202.xxx.yyy.0/25
> cache_peer_access proxyA.tanaka.co.jp deny net5
> cache_peer_access proxyB.tanaka.co.jp allow net5

 Henrik >You have to be patient when using this.
> It only works for IP addresses already in Squids internal
DNS cache.
> The effect is that it most likely won't work for the first
request,
> but it will start to work after a short while (and then
sporadically
> stop working for some requests when the internal DNS entry
expires).
> As a workaround you can use http_access to initiate the DNS
lookup.
>
>http_access deny net5 !all
>
>The above statement is always false, but triggers a DNS
lookup for
> net5 which will be cached and available in later
cache_peer_access
>processing.

[ Step2 ]

As there was no discription about never_direct contained in squid.conf,
I added next description in order to force proxy referring for net5.
But it didn't work.

never_direct allow net5

[ Step3 ]

Actually, there have been the discriptions about cache_peer_domain
in my squid.conf (shown as below Appendix A), we changed their
order of writing at around the part of line1560.
To be sure it worked, but cache_peer_domain configuration at line 200
didn't work.
Previous setting of squid.conf was the one removed line1010-
and line1120-, line1560- setting is 'before'.

--> I wonder HOW can we make use of cache_peer_domain
     and cache_peer_access parrallelly ??
     Here .dom1.tanaka.co.jp is related to xxx.yyy.zzz.0/25,
     and ACL name 'net5' is a part of ACL name 'local-server' ...
     I am very confused !
     Please follow this mail if you have any.
     Thank you for reading to the last !

[ SNIP ]
>--
>Henrik Nordstrom
>Squid hacker

Stray Sheep,
Masataka Tanaka@Sony Systems Design from Japan

 Appendix A --- Squid.conf of my own ---

line 200
            cache_peer_domain proxyA.tanaka.co.jp !.dom1.tanaka.co.jp
            cache_peer_domain proxyB.tanaka.co.jp .dom1.tanaka.co.jp

line 1010-
             acl net5 dst xxx.yyy.zzz.0/25
             http_access allow net5
             icp_access allow net5
             miss_access allow net5

line 1120-
             cache_peer_access proxyA.tanaka.co.jp deny net5
             cache_peer_access proxyB.tanaka.co.jp allow net5

line 1560-

   Before
             acl local-server dst xxx.0.0.0/25
             never_direct deny local-server
             never_direct allow net5
             never_direct allow all

   After
             never_direct deny local-server
             never_direct allow net5
             acl local-server dst xxx.0.0.0/25
             never_direct allow all
Received on Thu Nov 18 1999 - 01:14:41 MST