tis 2009-09-15 klockan 13:29 +0200 skrev Tobias Reckhard: > The problem I've got is that I don't know how to extend the Squid > configuration to redirect any requests to > https://www.somesite.com/somepath to the other back-end server. I've > tried a url_regex ACL and tying that to a second cache_peer, but it's > not working. Is the problem that "http://www.somesite.com/somepath"; is > encompassed by the dstdomain ACL above? If so, can I somehow > prioritise > ACLs or cache_peer statements in a fashion similar to http_access? Yes, it's exactly the same as http_access, but per cache_peer, filtering what may or may not be sent to that peer. cache_peer .... originserver name=apache cache_peer .... originserver name=glassfish acl somesite dstdomain www.somesite.com somesite.com acl glasspath url_regex ^/somepath cache_peer_access apache deny glasspath cache_peer_access apache allow somesite cache_peer_access glassfish allow somesite glasspath Regards Henrik
