Re: [squid-users] couldn't cache this image file

Thanks, Eliezer. But in which version you got that HIT?

I have already tried refresh_pattern, but I can't say if it is working
properly or not. I don't know how to test requests matching a
refresh_pattern, how can I see the changes made to the request or if
they're working...

But with or without refresh_pattern, it is always a MISS for me, in
3.3.12 or 3.3.8.

Well, I'm going to install a testing proxy machine, so I can mess with
it to see if I can manage to cache that and why it is not working now.

thanks,

Carlos

On Sun, Mar 16, 2014 at 7:37 PM, Eliezer Croitoru <eliezer_at_ngtech.co.il> wrote:
> It is being cached...
> 1395009265.334 0 192.168.10.125 TCP_IMS_HIT/304 309 GET
> http://s2.glbimg.com/XG7L47pX_ik0O_uxiV3g65rvpNU=/90x68/s.glbimg.com/jo/g1/f/original/2014/02/21/whatsapp.jpg
> - HIER_NONE/- image/jpeg
>
>
> I would try something like forcing a if modified since or something similar.
>
> Squid will contact the origin server to verify if being asked to
> http://www.squid-cache.org/Doc/config/refresh_pattern/
> The above contains couple nice options you can use.
> "ignore-reload ignore-must-revalidate" will might be the choice for this
> specific case but I would not recommed to understand it is good for
> everybody and for every case.
>
> Eliezer
>
>
> On 16/03/2014 14:35, Carlos Defoe wrote:
>>
>> Yes, I tried with 3.3.12, thinking that the vary bug could be the
>> problem... but it is still a MISS.
>>
>> 3.4 series is getting me in trouble, with 100% CPU, so for now I
>> discarded that. The problem is listed on some other threads... I tried
>> 3.4.1, 3.4.2, 3.4.3, and i couldn't find the problem yet. I have some
>> proxy servers with red hat 6, running on vmware hosts. But with no
>> squid packages, I compile the code with the options I need.
>>
>> The problem is that some files just can't get cached. I listed that
>> one, for example. It never gets cached. I think my HIT rate could be
>> better if some files like that, from a highly visited website here,
>> could be cached.
>>
>> thanks
>
>
Received on Mon Mar 17 2014 - 18:48:15 MDT