On 5/22/2013 7:11 PM, Alex Domoradov wrote:
Hello all, I have the following squid.conf acl parent_squid peername PARENT_SQUID acl FILE_TO_CACHE urlpath_regex \.(zip|iso|rar)$ acl TEST dstdomain storage.example.net cache_peer 192.168.100.50 parent 3128 3130 name=PARENT_SQUID connect-timeout=7 cache_peer_access 192.168.100.50 allow TEST FILE_TO_CACHE tcp_outgoing_address 192.168.100.1 parent_squid tcp_outgoing_address 192.168.1.2 http_port 192.168.100.1:3128 intercept When I run squid -k parse I got the following message # squid -k parse -f /root/xxx/squid.conf 2013/05/23 02:07:55| Processing Configuration File: /root/test/squid.conf (depth 0) 2013/05/23 02:07:55| squid.conf, line 107: No cache_peer '192.168.100.50'
Use name=PARENT_SQUID as in cache_peer_access PARENT_SQUID allow TEST FILE_TO_CACHE Eliezer
2013/05/23 02:07:55| Starting Authentication on port 192.168.100.1:3128 2013/05/23 02:07:55| Disabling Authentication on port 192.168.100.1:3128 (interception enabled) 2013/05/23 02:07:55| Disabling IPv6 on port 192.168.100.1:3128 (interception enabled) 2013/05/23 02:07:55| Initializing https proxy context If I removed name from cache_peer all works fine. Did I miss something? P.S. I have tested with squid-3.1.10 and squid-3.3.5
