Re: [squid-users] Squid icap respmod is not caching

Let say that on 3.2.0.1X it was working for me with ICAP respmod on with
youtube videos so it's not a RESPMOD problem unless...
There was a change in some of squid internals.
on squid 3.3 if i'm not wrong somebody told me that youtube caching
works but I have never seen that someone used my RESPMOD "no-store"
option so I am not 100% sure about it.
can you share the debug_options ALL,3 to understand what is going on?

What are you using ICAP for?

Eliezer

On 06/25/2013 02:17 PM, Paul Browne wrote:
> Hi,
>
> I will work on getting the headers / tcpdump & snoop logs) however just to be clear:
>
> 1) Squid 3.1 was caching our ICAP respmod responses and it was only when we went to the 3.2.7 version of squid did it fail to cache
>
> 2) curl is not an issue here, we tested it without respmod and it cached successfully,
>
> Regards
> -Paul
>
> -----Original Message-----
> From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
> Sent: 21 June 2013 01:28
> To: squid-users_at_squid-cache.org
> Subject: Re: [squid-users] Squid icap respmod is not caching
>
> On 21/06/2013 8:48 a.m., Eliezer Croitoru wrote:
>> ETAG???Vary??
>> There was a small talk about a bug in the vary thing But I am unsure
>> how it was tested.
>> Can we test this thing??
>
>
> And what HTTP status-line content is there?
>
> Also what headers is curl sending? curl in particular is known to force reload teh cache (which shows up as MISS).
> The request headers also can affect revalidation and the "X-Cache"
> headers do not report REFRESH/revalidate operations accurately.
>
> Unless we have the FULL set of request and respose headers paired together it is diffcult or impossible to identify what Squid is really doing.
>
> Amos
>
>
> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
> you may review at http://www.amdocs.com/email_disclaimer.asp
>
Received on Tue Jun 25 2013 - 16:37:08 MDT