Cryer,Phil wrote:
In a bid to get ICP to work I've noticed I didn't have htcp_access
defined. From the FAQ:
http://www.squid-cache.org/Versions/v2/2.6/cfgman/htcp_access.html
It tells us to use it just like http_access and shows the example:
htcp_access allow all
But when I add this line to my squid.conf and restart, it tells me
2007/10/19 15:46:33| parseConfigFile: line 55 unrecognized:
'htcp_access allow all'
The only thing I can think of is if this binary of Squid for RHEL4
wasn't compiled with support for that. Is this a switch that needs to
be added, or should it just be there anyway?
Needs to be added. But that won't help...
Details of my build:
bash-3.00# /usr/sbin/squid -v
Mmmm. Running as root? Do be careful.
Squid Cache: Version 2.6.STABLE13
SNIP
Still unsure of if this will make our squids talk to each other,
instead, if they don't have the page they don't check with eachother,
just just go to the origin server with the FIRST_PARENT_UP message.
Relevant lines:
cache_peer nsdgecmweb-18.appl.devjones.com parent 80 0 no-query
no-netdb-exchange no-digest originserver login=PASS
cache_peer nldg-28.appl.devjones.com sibling 3128 3130 proxy-only
login=PASS no-query default
I think this might have a lot to do with the issue. Check those
cache_peer parameters again. proxy-only, fine. login=PASS, fine.
no-query, not so fine. You are explicitly telling your cache NOT to
check with its sibling for cached data. Specifying ICP or HTCP as the
protocol you are not using won't change anything... :o)
acl fromneighbor src 192.168.120.226
#cache_peer_access nldg-28.appl.devjones.com deny fromneighbor
cache_peer_access nldg-28.appl.devjones.com allow fromneighbor
icp_access allow all
log_icp_queries on
That's going to be a mighty quiet log if nldg-28.appl.devjones.com is
set up the same way.
Thanks all.
P
Chris
