Thanks Amos, Our system is a custom product design with some special requirements, so we ended up with the such configuration and somewhat customized Squid. We thought that perhaps some easy way around might be available but at the end this is not very critical issue for us. Andrew -----Original Message----- From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] Sent: Friday, September 21, 2012 3:24 AM To: squid-users@xxxxxxxxxxxxxxx Subject: Re: Cache Manager working on Apache server as ICP sibling On 21/09/2012 3:33 a.m., Andrew Krupiczka wrote: > 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. Apache is not a server which can maintain a proxy cache. Why are you making it a sibling (potential alternative *cache*) instead of a parent (potential data *source*)? Amos
