[squid-users] dynamic content wont cache in reverse-proxy

I have squid 2.6.20 running on centos, reverse-proxying for dynamic
content...but items are not getting cached. I've run a similar
http-accel setup with 2.5 at least a year back and didnt have this
problem...has something changed since then?

I've checked the headers from the origin servers, and all the reply
text/xml is pretty standard and cacheable. Only tweaked header is the
expire time, which is set by the origin to be 5 minutes.

Request uri's are long, i.e.
/sd/api/somethingservice/9.99/totallyFakeStrings?PID=wsC5tRszzna55EgsS2m1Jpua9-Xbb-FTIh7EDiZd%19endItAll=39

access.log is full of TCP_MISS and UDP_MISS...with heavy load tests I
see some TCP_MEM_HITS, but the only TCP_HITS I see are related to
siblings requesting digests. store.log is full of RELEASE's and
devoid of SWAPOUTs :(

Here are relevant portions of my config:

       http_port 80 accel vhost defaultsite=my.server.wherever.com
       icp_port 3130

       cache_peer 9.9.9.9 parent 80 0 no-query originserver name=HostAccel
       cache_peer 1.1.1.2 sibling 80 3130 proxy-only
       cache_peer 1.1.1.3 sibling 80 3130 proxy-only

       cache_dir aufs /cache1 8192 16 256
       cache_dir aufs /cache2 8192 16 256
       cache_dir aufs /cache3 8192 16 256
       cache_dir aufs /cache4 8192 16 256
       store_dir_select_algorithm round-robin

       refresh_pattern . 0 20% 4320

       acl our_site dstdomain my.server.wherever.com
       acl all src 0.0.0.0/0.0.0.0
       acl origin dst 9.9.9.9
       acl siblings src 1.1.1.2 1.1.1.3
       acl acceleratedPort port 80

       cache allow all
       http_access allow our_site
       http_access allow origin acceleratedPort
       http_access allow siblings
       http_access deny all
       http_reply_access allow all
       icp_access allow siblings
       icp_access deny all

       visible_hostname my.server.wherever.com
       unique_hostname squid01

       client_db off
       uri_whitespace allow
       strip_query_terms off
       relaxed_header_parser warn
       icp_query_timeout 500

Can anyone tell me why nothing seems to be getting cached? Is there
an inherent rejection of dynamic content now? I hope not, some of us
rely on caching systems to smooth out the spikes in demand on our web
services :)

Thanks in advance,

- G
Received on Fri May 16 2008 - 16:18:11 MDT