On 11/07/2013 01:16 AM, WorkingMan wrote: > adaptation_access eReqmod allow GOOD_HTTP_STATUS > > cache.log: says ACL is used but htere is no HTTP reply -- not matching. Exactly. You are asking Squid to predict what the future response status code will be. Squid cannot predict the future. At pre-cache REQMOD time, the response does not exist yet. Moreover, if an adapter changes the request, the response may be different (and may even come from the adapter itself!). You may want to draw a diagram of what Squid does when processing a typical miss request. The sketch below simplifies things a little and omits message body processing, but can be used as a starting point: * receive virgin request headers from the client * start request adaptation * send adapted request headers to the next hop * receive virgin response headers from the next hop * start response adaptation * send adapted response headers to the client I recommend testing with an "all" ACL. When everything else works, replace it with a more selective ACL (if such an ACL exists). HTH, Alex. P.S. You do not need the adaptation_service_set line.
