Revision: 14422 Author: adrian.chadd Date: Fri Feb 19 19:52:10 2010 Log: Comment what the dstfwdip ACL will be.
This raises a good question - how will the ACL be properly evaluated? If the ACL is parsed and handled before the HIT becomes a MISS, all kinds of potential issues creep up. This must thus be used not in http_access, but in miss_access. I'll have to note that somewhere. http://code.google.com/p/lusca-cache/source/detail?r=14422 Modified: /branches/LUSCA_HEAD/src/cf.data.pre ======================================= --- /branches/LUSCA_HEAD/src/cf.data.pre Tue Feb 16 20:13:42 2010 +++ /branches/LUSCA_HEAD/src/cf.data.pre Fri Feb 19 19:52:10 2010 @@ -515,6 +515,7 @@ acl aclname src addr1-addr2/netmask ... (range of addresses) acl aclname dst ip-address/netmask ... (URL host's IP address) acl aclname myip ip-address/netmask ... (local socket IP address) + acl aclname dstfwdip ip-address/netmask .. (IP of the forwarded host) acl aclname arp mac-address ... (xx:xx:xx:xx:xx:xx notation) # The arp ACL requires the special configure option --enable-arp-acl. -- You received this message because you are subscribed to the Google Groups "lusca-commit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/lusca-commit?hl=en.
