I would love to get some time to test Apache 2.1. Unfortunately we already have our share of problems with the stability of Apache 2.0. By stability I do not mean that the software does not work or crashes, but that there are so many changes from one Apache release to another (especially with mod_cache which is experimental) that we spend a significant amount of time testing, patching and retesting for every internal release we make. We are also using third-party modules that currently do not support Apache 2.1. Do you know whether the 2.1 mod_cache is compatible with Apache 2.0 ? -ascs -----Original Message----- From: Joshua Slive [mailto:jslive@xxxxxxxxx] Sent: Friday, July 29, 2005 5:13 AM To: users@xxxxxxxxxxxxxxxx Subject: Re: [users@httpd] Apache 2.0: mod_cache: "Cache-Control: no-cache" not preventing content from being served from cache On 7/28/05, Axel-Stéphane SMORGRAV <Axel-Stephane.SMORGRAV@xxxxxxxxxxxxxx> wrote: > As far as I have understood RFC2616 14.9.1 and 14.9.2, no-cache is supposed to prevent content from being served from cache without revalidation, and no-store forbids storing content altogether. > > Tests I made with Apache 2.0.49 and 2.0.54 show that Apache gladly serves contents containing "Cache-Control: no-cache" in the response header, from cache without revalidation. On the other hand, if the response contains "Cache-Control: no-store", the response is not cached. > > I submit that the CACHE_OUT filter should not be run if the cached headers contain "Cache-Control: no-cache". > > Any thoughts? Don't know about that specific issues, but you should try httpd 2.1 where mod_cache has been vastly improved. Joshua. --------------------------------------------------------------------- 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
|