Re: [squid-users] parent cache

From: <Jim_Brouse/PYT@dont-contact.us>
Date: Wed, 27 Oct 2004 16:44:14 -0700

I added the below text to the child:

nonhierarchical_direct off
prefer_direct off
cache_peer parent.server.ip parent 3128 0 default no-query

And I added the child to an acl on the parent that does not allow
downloading of .exe's but when I tried to downoad them I was able to.
Since I added the child to an acl on the parent that does not allow
download of exe's I do not see why I can download exe's.

I thought since the child was added on the parent to an acl that did not
allow downloads of exe's I would not be able to download them.

To recap:

From child squid server given workstation IP can download anything
Put child squid server IP into an acl on the parent server that can not
downoad .exe's
From given workstion IP I can download .exe's but why?

Jim

                                                                                                                                              
                    Henrik
                    Nordstrom To: Jim_Brouse/PYT@PASCUAYAQUITRIBE.ORG
                    <hno@squid-cac cc: squid-users@squid-cache.org
                    he.org> Subject: Re: [squid-users] parent cache
                                                                                                                                              
                    10/27/2004
                    03:46 PM
                                                                                                                                              
                                                                                                                                              

On Wed, 27 Oct 2004 Jim_Brouse/PYT@PASCUAYAQUITRIBE.ORG wrote:

> I have been reading documentation at the below two urls and what I can
not
> determine is that do I need to enable something on server a if it is
going
> to be a parent to server b or do I just need to tell server b which
server
> is its parent?

You need to make A allow B as a client if it is not already in the list of
allowed clients, and to configure B to use A as it's parent.

No other configuration on A is required.

> cache_peer parentcache.foo.com parent 3128 0 no-query default
> acl all src 0.0.0.0/0.0.0.0
> never_direct allow all
>
> or
>
> cache_peer parentcache.foo.com parent 3128 0 no-query
> prefer_direct off

Depends on what you want. The first always uses the parent, the second
prefers to use the parent if available and it makes sense for the request
in terms of caching, if not it will go direct.

Regards
Henrik
Received on Wed Oct 27 2004 - 17:44:22 MDT

This archive was generated by hypermail pre-2.1.9 : Mon Nov 01 2004 - 12:00:02 MST