On 22/03/2012 12:58 a.m., Erik Svensson wrote:
Hi,
I run the test again with debug_options set as Amos recommended.
Thank you. That confirmed there is something very funky going on. No
timstamp, caching controls or cross-worker limits going on there. It
really should be caching.
Amos
Hi,
I tried setting a very permissive refresh_pattern - but squid still
refuses to cache.
Then I tried creating a small disk cache. In the real production environment
we use memory cache only.
cache_dir ufs /tmp/3/cache 4 1 1
And now the objects gets cached !
[root@sesxsp01wintc 3]# cat acce
Hi,
I run the test again with debug_options set as Amos recommended.
Here is the cache.log :
2012/03/21 12:37:44 kid1| Starting Squid Cache version 3.2.0.16 for
i686-pc-linux-gnu...
2012/03/21 12:38:34.644 kid1| HTTP Client local=127.0.0.1:9993
remote=127.0.0.1:42828 FD 10 flags=1
2012/03/21 12:3
Hi Amos,
Since last 2-3 months i am testing squid 3.2 with different version till
current latest version, And i observed that 3.1 is working fantastic
while we are looking for cache gain / cache hit.
Again, i say squid 3.1 is awesome for people who wants cache hit /
bandwidth saving.:-)
Re
cc'ing to squid-dev where the people who might know reside
Also, adding "debug_options 11,2" may show something useful in the HTTP
flow for 3.2.
Amos
On 15.03.2012 05:59, Erik Svensson wrote:
Hi,
Objects don't get cached in Squid 3.2. Same transactions and config
works in 3.1
I will
Hi,
Objects don't get cached in Squid 3.2. Same transactions and config works in 3.1
I will show my problem with a simple webserver listening on 127.0.0.1:9990
and sending transactions from curl to a squid listening on 127.0.0.1:9993
3.1 logs first a MISS since the cache is empty and when repeat
