Would you mind sharing your frustration about Squid with me off the list (since it is not really relevant for this forum) ? I have no practical experience with Apache 2.2.0, but I have been using the cache module of Apache 2.0 extensively in a reverse-proxy configuration for a couple of years. One thing that has really bugged me in Apache 2.0 is that "Cache-Control: no-cache" is not enforced when this directive appears in a response. According to RFC2616 14.9.1, a response containing this directive is cacheable but must be revalidated prior to being used to satisfy subsequent requests. By judging from the code, this is still the case in 2.2.0. Apache will therefore happily serve a response containing a no-cache directive without revalidation. In order to work around this problem, I have modified the code so that no-cache is treated the same as no-store in responses. Since I am using 2.0 in which mod_cache was experimental, and the standard answer whenever you ask questions about that version of mod_cache is "upgrade to 2.2 because the module has been totally reworked", I have not bothered to file a bug. I am wondering whether mod_cache is quite mature yet. It does not quite give me the warm and fuzzy feeling I would like to have about a piece of software which I put into production. Squid however, has been used as a HTTP cache for a significant length of time, and I feel more confident about its caching algorithms than I do about mod_cache. -ascs -----Original Message----- From: Dan Price [mailto:dp@xxxxxxxxxxx] Sent: Tuesday, April 18, 2006 1:46 AM To: users@xxxxxxxxxxxxxxxx Subject: [users@httpd] Problems with Apache 2.2.0 as a conventional proxy Hi, After years of frustration with Squid, I'm now using 32-bit Apache 2.2.0 as a caching web proxy for my group. The underlying OS is 64-bit Solaris 10 running on Opteron. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|