"Axel-Stephane SMORGRAV" wrote:
> You are exactly right. However, the real question is: why does the request
> contain
> that max-age directive?
Because the "Reload" button was hit in Firefox. Try simply to just hit
"Enter" in the URL bar or copy/past the URL into a new tab, you will
find the ma
anche 9 décembre 2007 22:18
À : users@httpd.apache.org
Objet : Re: [EMAIL PROTECTED] Reverse proxy cache control problems
After reading a bit more on what RFC 2616 says about Cache-control I figured
out it was apparently the
Cache-Control: max-age=0
header the browser was sending that made mod_
After reading a bit more on what RFC 2616 says about Cache-control I
figured out it was apparently the
Cache-Control: max-age=0
header the browser was sending that made mod_cache not use the cached
copy even though the server was returning
Cache-Control: max-age=3600
After switching the lin
Axel-Stephane SMORGRAV wrote:
> Could you possibly post the headers returned by \
> http://localhost:5050/cachetest/jsp/cacheable/main.jsp along with
your proxy \
> configuration directives?
After upgrading Apache from 2.2.4 to 2.2.6 the debug log looks a bit
different but the test page stil
-Message d'origine-
De : Marko Asplund [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 6 décembre 2007 21:56
À : users@httpd.apache.org
Objet : [EMAIL PROTECTED] Reverse proxy cache control problems
hi
I'm trying to cache dynamically
hi
I'm trying to cache dynamically generated content using an Apache 2.2
reverse proxy.
Apache proxies content coming from Tomcat through AJP protocol.
For some reason mod_cache determines that cacheable content is not fresh
and refetches the content
though the application sets the Expires and