I was able to get it working by making the squid user the owner of the file.
The upgraded squid server, however, still seems to be an issue some files
returned by the cache, as some appear complete yet have a Content-Length
value of 0, so they don't work. At this point I am thinking that the faul
>Please upgrade. Current Squid-4 release is 4.9 and there are quite a few
>very major security issues and bugs resolved since 4.2. Some of which
>are related to cache corruption.
I have tried using squid 4.9, however am having an issue with the url
rewriter I am using to translate the urls into ra
I have an odd issue running squid 4.2 as a reverse proxy in front of
rackspace cloudfiles. For some reason, something went wrong when the request
was made initially and squid has cached a broken response. The headers
returned by squid are as follows:
HTTP/1.1 200 OK
Accept-Ranges: bytes
Last-Modif
