[squid-users] Does squid's icap client support X-Server-IP in ICAP header ?

[Hsuan Yu]

Thx for reply, Alex

%ts works both in REQMOD and RESPMOD, %>a is OK too.

So it seems that %<a has a bug for or lack of support,

is there another way to carry ORIGINAL_DST in access.log into ICAP header
using X-Server-IP?


2015-09-08 13:26 GMT+08:00 Alex Rousskov <rousskov at measurement-factory.com>:

> On 09/07/2015 10:08 PM, Hsuan Yu wrote:
>
> > I didn't see relevant icap config options in squid.conf to carry
> > X-Server-IP in ICAP header
>
> Squid currently has built-in support for X-Client-IP, not X-Server-IP.
>
>
> > So I tried to use adaptation_meta X-Server-IP: "%<a" in squid
> > 3.5.8/squid 4.x
> >
> > but not working, I only got the result like following:
> >
> > X-Server-IP: -
>
>
> In REQMOD, this is expected because %<a is the IP address of the last
> server or peer connection (and there may be no origin server or peer
> connection at REQMOD time).
>
> In RESPMOD, this may indicate a bug or lack of support for that %code.
> If you are using RESPMOD, do other, simpler %codes like %ts work in your
> adaptation_meta configuration? Please quote your exact adaptation_meta
> configuration line, just in case.
>
>
> HTH,
>
> Alex.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150908/689f14c6/attachment.html>