it is showing up as a single html block on the user side, so the caching is only working internal to your server.
It isn’t working in downstream proxies or the user browsers, this causes you to have to reserve the entire page.
This is what we get from userland.
Raw request
GET http://www.freerepublic.com/tag/*/index HTTP/1.0
User-Agent: Opera/9.80 (Windows NT 6.0; U; en) Presto/2.5.24 Version/10.53
Host: www.freerepublic.com
Accept: text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1
Accept-Language: en-US,en;q=0.9
Accept-Charset: iso-8859-1, utf-8, utf-16, *;q=0.1
Accept-Encoding: deflate, gzip, x-gzip, identity, *;q=0
Cookie: __utmz=217263553.1277242371.2343.3.utmccn=(referral)|utmcsr=209.157.64.200|utmcct=/perl/login|utmcmd=referral; FOCUS=41522%3AHfZgoOwP4uJPAp6P5QExMZ%3A1; __utma=217263553.516295404.1232848598.1277258150.1277262665.2346; __utmc=217263553; __utmb=217263553
Cookie2: $Version=1
Pragma: no-cache
Cache-Control: no-cache
Proxy-Connection: Keep-Alive
Raw Response
HTTP/1.0 200 OK
Date: Tue, 22 Jun 2010 22:39:55 GMT
Server: Apache
Cache-Control: private
Content-Type: text/html; charset=latin1
X-Cache: MISS from zoolife
X-Cache-Lookup: MISS from zoolife:3128
Via: 1.1 zoolife:3128 (squid/2.7.STABLE7)
Connection: close
If there was an html blocks, each thread would show up as a separate html docs.
Instead what we get is a single html block.
Cache requires that these each be separate html blocks
Whatever. We use a caching system. We couldn’t run without it. The recent slowdown had nothing to do with caching. It was due to a major hardware crash.
http://www.alexa.com/siteinfo/freerepublic.com
Average Load Time for Freerepublic.com
Very Fast (1.038 Seconds), 80% of sites are slower.