when using squid with ICP enabled in a hierarchy sourcehash will not be handeled correct. our setup: PC > user-proxy > proxy-inter 1 > proxy-inter 2 > dmz-proxy 1 proxy-inter 3 > dmz-proxy 2 proxy-inter 4 > PC will connet to his user-proxy. in "user-proxy" there are 4 parent proxies (proxy-inter 1 to 4) configured. icp_port 3130 cache_peer proxy-inter1 parent 8083 3133 sourcehash no-digest no-netdb-exchange connection-auth=off cache_peer proxy-inter2 parent 8083 3133 sourcehash no-digest no-netdb-exchange connection-auth=off cache_peer proxy-inter3 parent 8083 3133 sourcehash no-digest no-netdb-exchange connection-auth=off cache_peer proxy-inter4 parent 8083 3133 sourcehash no-digest no-netdb-exchange connection-auth=off all of the proxy-inter1 to 4 will have icp_port 3133 cache_peer dmz-proxy1 parent 8083 7 sourcehash no-query no-digest no-netdb-exchange cache_peer dmz-proxy2 parent 8083 7 sourcehash no-query no-digest no-netdb-exchange so user-proxy can use ICP-queries to his 4 parents "proxy-inter1-4" to get content. I can see icp-queries in the access.log. my problem is now: when I enable icp-queries sourcehash will not be honored correctly. on the webserver which I will access from PC I can see both ip-addresses from dmz-proxy1 and dmz-proxy2. when I disable icp-queries on user-proxy I will only see one ip-address from dmz-proxy1 (justa as an example) on the webserver. so without icp-queries sourcehash will be honored in the complete hierarchy. with icp-queries sourcehash get mixed. markus
