RE: [squid-users] Cache Manager working on Apache server as ICP sibling

Thanks,

To be more precise my Apache server peer is configured as: cache_peer 127.0.0.1 sibling 1114 3130 no-digest originserver

The Cache Manager only works after adding the following line: neighbor_type_domain 127.0.0.1 parent AKDME7071BCE29DE9

which "transforms" my sibling peer into to the parent peer which we don't want to do.

Andrew

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Wednesday, September 19, 2012 11:19 PM
To: squid-users_at_squid-cache.org
Subject: Re: [squid-users] Cache Manager working on Apache server as ICP sibling

On 20/09/2012 7:46 a.m., Eliezer Croitoru wrote:
> On 9/19/2012 10:26 PM, Andrew Krupiczka wrote:
>> In our product we're running the Squid 2.7 and Apache http server on
>> a single machine.
>> The Apache server can originate a content and is configured as
>> Squid's cache_peer sibling to be queried via ICP.
>> We can run the Cache Manager script and access it, if the Apache
>> server is reconfigured as parent but are unsuccessful otherwise.
>> Do you think is that possibility at all?
>> Thanks,
> Siblings by default arn't queried for content unless you define a
> never_direct allow acl on the url of cachemgr.
>
> what problem are you getting while trying to fetch cachgmgr?
> In anycase I think that fetching cache mgr throw the squid from the
> apache is a bad idea.

No more good or bad than any other website. cachemgr.cgi is just a web page script after all.

The key thing is that Apache is an *origin*, not a sibling. Origins are configured in Squid-2.7 as a parent with "originserver" flag.

Amos
Received on Thu Sep 20 2012 - 15:34:07 MDT