On 06/22/2018 03:14 AM, chgerber wrote:
>>> 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.
> Why are you so sure that %note sho
>> 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
On 06/05/2018 09:48 AM, chgerber wrote:
>> 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:: I am not sure if "my-ecap-header" is a
> really a header as I called it as I hand i
On 06/05/2018 04:51 AM, Amos Jeffries wrote:
> The adaptor API purpose is to alter HTTP messages as they travel through
> the proxy, not to be a substitute for access control logic already
> available in the proxy.
This statement is incorrect for legitimate use cases where the required
access con
> 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
On 06/05/2018 05:29 AM, chgerber wrote:
> 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 all requests
> containing a certain string "foo".
You cannot satisfy the above requirement
On 06/05/2018 03:27 AM, chgerber wrote:
> "It is best to use %note logformat %code for logging annotations.
> The %adapt:: to work around the current ICAP code lack of support for annotations)."
> How exactly can I use %note to log the same information to access.log? For
> example assume I use "
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
On 05/06/18 21:27, chgerber wrote:
> "It is best to use %note logformat %code for logging annotations.
> The %adapt:: to work around the current ICAP code lack of support for annotations)."
>
> How exactly can I use %note to log the same information to access.log? For
> example assume I use "%{m
"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
On 09/27/2017 11:52 PM, Christof Gerber wrote:
> I have a question concerning eCAP implementation in Squid 3.5.
Actually, you do not :-). You have a question about using so called
annotations in Squid error pages. eCAP is just one of several annotation
sources in Squid. The other sources are ICAP
Hi Squid users
I have a question concerning eCAP implementation in Squid 3.5.
My goal is to display data which is provided by an eCAP adapter on a Squid
error-page. My primary goal is to achieve this with the eCAP transaction
meta-information which is provided by the eCAP adapter with
Adapter::Xa
12 matches
Mail list logo
