I have another related question: I can see my cache filling up, but I'm sending about 7 gigs through the proxy, and the cache doesn't even have 300 MB in it yet, and the transfer is at 62%.
Looking in the store.log, I see a mix of RELEASE and SWAPOUT lines. Also, none of the files are > 2 GB. Anyone have any ideas why all the files aren't getting cached? Did I miss something in my config file? Thanks for your time, -Adam -----Original Message----- From: Volker-Yoblick, Adam [mailto:avol...@ea.com] Sent: Thursday, December 09, 2010 5:51 PM To: 'squid-users@squid-cache.org' Subject: [squid-users] RE: Forcing squid to cache files Doh! I feel like a moron. Read up on the refresh_pattern command, and it seems that first 0 on the last line was causing everything to be marked as "not fresh" right away. I upped that value, and my cache is now filling up. Nothing to see here.... =) -----Original Message----- From: Volker-Yoblick, Adam [mailto:avol...@ea.com] Sent: Thursday, December 09, 2010 5:42 PM To: 'squid-users@squid-cache.org' Subject: [squid-users] Forcing squid to cache files Greetings squid users, I recently installed squid 3.1.9 on an RHEL 5 server, with no options when running ./configure. We have a proprietary tool that sends files from one machine to another over HTTP, and I wanted to have squid always cache the files to help improve transfer times when the tool is used from outside the building. Note that this cache will NEVER be used to serve webpages, so I don't care about violating HTTP protocol. I was able to set up the acls to allow a source connection from my machine, and to allow a destination connection to another machine. I can tell this is working, because when I start the transfer, I see lots of HTTP GET lines in my access.log. I also see lots of lines in my store.log, but unfortunately, all the lines are RELEASE lines, meaning nothing is being stored in the cache. I verified this by running du -hs on my cache dir, and the size is never going up. I've spent most of the day googling this issue (and looking at the squid FAQ), and it seems most users have the problem where they are not ignoring "no-cache" commands in the http headers. I tried to get around this in my squid.conf, shown below: refresh_pattern ^ftp: 1440 20% 10080 override-expire override-lastmod ignore-reload ignore-no-cache ignore-no-store ignore-must-revalidate ignore-private refresh_pattern ^gopher: 1440 0% 1440 override-expire override-lastmod ignore-reload ignore-no-cache ignore-no-store ignore-must-revalidate ignore-private refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 override-expire override-lastmod ignore-reload ignore-no-cache ignore-no-store ignore-must-revalidate ignore-private refresh_pattern . 0 20% 4320 override-expire override-lastmod ignore-reload ignore-no-cache ignore-no-store ignore-must-revalidate ignore-private This doesn't seem to fix the problem, however. I also made sure that the "squid" user is the owner of my cache_dir, and I made sure that cache_effect_user is set to "squid". Running squid -z returns no errors. I'm kinda stumped at this point. Anyone have any suggestions? Maybe a "gotcha" that I missed, or proper steps to debug this further? Thanks for your time, -Adam
