Re: [squid-users] CRASH with CACHE_PEER_ACCESS settings

[Henrik Nordstrom]

On Tue, 31 May 2005, Kia T. Vang wrote:


I am running squid as a reverse proxy.  SQUID crashes with the following
cache_peer_access settings:

cache_peer 10.0.0.11 parent 8080 7 originserver no-query
front-end-https=auto name=www1 acl webmail dstdom_regex -i ^webmail\..*
cache_peer_access www1 allow webmail

I'm using the current CVS version for SQUID 3 on Fedora Core 3.


Please try again with a current Squid-3 snapshot.

The ACL subsystem has been somewhat broken in Squid-3 for some time in 
many acl driven directives outside http_access.. a workaround was applied 
some time ago (but after your question).


Regards
Henrik

[squid-users] CRASH with CACHE_PEER_ACCESS settings

[Kia T. Vang]

Hi,

I am running squid as a reverse proxy.  SQUID crashes with the following
cache_peer_access settings:

cache_peer 10.0.0.11 parent 8080 7 originserver no-query
front-end-https=auto name=www1 acl webmail dstdom_regex -i ^webmail\..*
cache_peer_access www1 allow webmail


So, when I access my site http://webmail.foo.com/ SQUID crashes with a
message 'Aborted'.

Now, if I replace cache_peer_accss with cache_peer_domain instead,
everything works fine.  For example:

cache_peer_domain www1 webmail.foo.com

I'm using the current CVS version for SQUID 3 on Fedora Core 3.