>> If it does not work, then most likely there is a bug in your adapter, in
>> your Squid configuration, or in Squid.
By now I see no other way than this being a misunderstanding between us or a
bug in Squid 3.5.
##
Squid 3.5 XactionRep.cc line 492:
// Store received meta headers for a
> logformat myLog ... adapter-decision=%{my-ecap-header}note ...
> access_log ... myLog ..
I tried this but it didn't work as it does with
"%{my-ecap-header}adapt::http://www.squid-cache.org/Versions/v3/3.5/cfgman/logformat.html
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.c
Does that mean it is possible to apply ACL to headers/notes after ecap
processing or not?
I agree with your efficiency considerations but can you tell me how you
would solve the following requirement with squid and without eCAP/ICAP:
Parse the body of all requests with a non-empty body and block
"It is best to use %note logformat %code for logging annotations.
The %adapt::http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinf
