Aha, just came across another discussion that included this info (would be great to include this in the documented config file under url_rewrite_program). So for anyone who might search this in the future:
Sequence is approximately * Request accepted * http_access Access controls * URL rewriting, replacing Squid's idea of the URL * http_access2 Access controls * Cache lookup * Forwarding on cache miss * http_reply_access Reply access controls >From discussion: http://squid-web-proxy-cache.1019090.n4.nabble.com/url-rewrite-and-cache-whi ch-URL-should-be-cached-td1023682.html -----Original Message----- From: David Parks [mailto:[email protected]] Sent: Wednesday, September 15, 2010 8:39 PM To: [email protected] Subject: [squid-users] When is the url_rewrite_program called? When is the url_rewrite_program called? Is it before ACL matches occur? Or after the http_access tag is matched? I'm just trying to figure out the flow of events that occur. Looking for an answer like: 1) http_access is matched, if denied end 2) url_rewrite_program called 3) acls are matched a second time 4) http_access is matched a second time Thanks, David
