Search squid archive

both ACL dstdomain and myport exist

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



dear Squid gurus,

I want to set up an accelerator of squid for these cases:

www.example.com:80    =>   172.16.0.100:80
www.example.com:8080  =>   172.16.0.100:8080
library.example.com   =>   172.16.0.101


I have the clues to use both dstdomain and myport ACL, like below:

cache_peer 172.16.0.100 parent 80 0 no-query originserver name=portsw_1
acl port_1 myport 80
cache_peer_access portsw_1 allow port_1

cache_peer 172.16.0.100 parent 8080 0 no-query originserver name=portsw_2
acl port_2 myport 8080
cache_peer_access portsw_2 allow port_2

cache_peer 172.16.0.101  parent 80 0 no-query originserver name=library
acl thelib dstdomain library.example.com
cache_peer_access library allow thelib


But, these config will cause the conflict, am I right?
For example, when user requests:

http://library.example.com/

Squid doesn't know it will forward the request to 172.16.0.100 or 172.16.0.101, since both myport and dstdomain ACLs are matched.

Please help, thanks.

Regards,
Wah.


      Access Yahoo!7 Mail on your mobile. Anytime. Anywhere.
Show me how: http://au.mobile.yahoo.com/mail


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux