[squid-dev] StoeiD and ICAP services callouts, when it happens?

Alex Rousskov rousskov at measurement-factory.com
Thu Jul 12 20:09:35 UTC 2018

On 07/12/2018 11:21 AM, Eliezer Croitoru wrote:

> With regular logformat I am using:
> %{X-Store-Id}>ha
> And it works perfect.

%>ha does not log an ICAP response header. It logs an HTTP request
header. You asked about an ICAP response header.

> So I tried using the next config line for store id:
> store_id_extras "%>a/%>A %un %>rm myip=%la myport=%lp %{X-Store-Id}>ha"
> which didn't worked as expected since it sends always "-".

Bugs notwithstanding, the above should work if your adaptation service
adds an X-Store-ID request header field to the adapted HTTP request. You
can check what headers Squid has for %>ha by specifying %>ha without any

> I have now tried to understand what and how I should use the:
> %adapt::<last_h

Yes, %adapt::<last_h should work for logging the last ICAP response
header. Have you tried specified that logformat code, without any



> -----Original Message-----
> From: Alex Rousskov [mailto:rousskov at measurement-factory.com] 
> Sent: Thursday, July 12, 2018 7:01 PM
> To: Eliezer Croitoru <eliezer at ngtech.co.il>; squid-dev at lists.squid-cache.org
> Subject: Re: [squid-dev] StoeiD and ICAP services callouts, when it happens?
> On 07/12/2018 03:16 AM, Eliezer Croitoru wrote:
>> is it possible to pass an ICAP response header into the store_id_extras?
> Yes, %adapt::<last_h should work in store_id_extras:
> https://wiki.squid-cache.org/SquidFaq/OrderIsImportant#Callout_Sequence
> Alex.

More information about the squid-dev mailing list