Perrin Harkins wrote:
[forgot to CC the list]
On Thu, May 13, 2010 at 3:56 AM, Michel Jansen
<michel.jan...@web-ict.com> wrote:
Tha pages are cached by the browser..
Ok. First, you don't need the err_headers_out call, because no_cache
already does that for you.
I'd suggest checking the headers you're sending with a browser plugin,
LWP, or telnet. If the cache control headers are being sent but the
browser is ignoring them, try setting an Expires header.
For whatever it may help to say this : in my experience with many
customers and many corporate browsers and web firewalls/proxies, the way
in which browsers and proxies decide to cache or not a given page,
/should/ be clear according to the HTTP RFCs, but is quite unpredictable
in the practice.
This is not a mod_perl issue, nor an Apache issue, not even an issue of
your application, it is just a reality. The best you can do is follow
the RFC, see if it works, and if not tweak your headers in function of
one particular situation. But there is no "universal truth" here.
