On 27/11/19 11:24 am, --Ahmad-- wrote: > Hello Floks , > > > i have squid ACL/TCP Outgoing based on incoming header . > > as an example below : > > > acl requestheader5000 req_header X-Proxy 1.2.3.4 > acl requestheader5001 req_header X-Proxy 1.2.3.5 > acl requestheader5002 req_header X-Proxy 1.2.3.6 > acl requestheader5003 req_header X-Proxy 1.2.3.7 > > ######################### > > tcp_outgoing_address 1.2.3.4 requestheader5000 > tcp_outgoing_address 1.2.3.5 requestheader5001 > tcp_outgoing_address 1.2.3.6 requestheader5002 > tcp_outgoing_address 1.2.3.7 requestheader5003 > > > So if an incoming request with X-Proxy header 1.2.3.4 , it will match the Acl requestheader5000 and will have outgoing address as 1.2.3.4 . ——> no problem here . > > > > Now Say the incoming X-Proxy header was 9.9.9.9 which is a value not matched in the current ACL . > > How can we let squid to send those Type of requests “ not match with ACL “ to remote Cache peer squid in case not “ matched X-proxy header” ? > You are mixing up concepts here. tcp_outgoing_address sets the address the TCP packets say they are coming *from*. It has nothing to do with where they are going *to*. For controlling which requests go to a peer use <http://www.squid-cache.org/Doc/config/cache_peer_access/>. With maybe one or more of these directives as well, depending on your configuration complexity and exact routing policy: <http://www.squid-cache.org/Doc/config/always_direct/> <http://www.squid-cache.org/Doc/config/never_direct/> <http://www.squid-cache.org/Doc/config/prefer_direct/> <http://www.squid-cache.org/Doc/config/nonhierarchical_direct/> Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
