-request;
$r-no_cache(1);
$r-no_cache(0);
$r-send_http_header;
With mod_perls 1.24_01 and 1.25 on Apaches 1.3.14 and 1.3.19, this call
leaves me with Pragma and Cache-Control headers. Sadly, the nice (but
broken as per above) no_cache() behavior of sending those two headers is
also
in my setup, even with
no_cache(0) I have
Pragma: no-cache
Cache-control: no-cache
which seems counter-intuitive to me.
I've checked the Eagle : it says that no_cache() only adds an Expires
field.
Ok. But then from where does the Pragma header come ?
About -headers_out() it is specifically said
Apache (as in httpd) will set the 'Expires' header to the same value as the
'Date' header when no_cache is flagged in the request_rec. When your Perl
handler sets $r-no_cache(1), mod_perl (in Apache.xs) is setting the
'Pragma: no-cache' and 'Cache-control: no-cache' headers in addition
r browsers and versions)
but NOT Netscape 4.x have absolutely no respect for cache-control.
My code does this:
$r-no_cache(1);
# some code to calculate a date 10 years ago (!) goes here...
$r-header_out(
'Expires' = "$day_text, $day $mon_text $year $hour:$min:$sec GMT"
);
$r-send
The problem I have is that IE5 (and perhaps other browsers
and versions)
but NOT Netscape 4.x have absolutely no respect for cache-control.
IE5 can be set up to ignore any cache directives and keep a document
for either the duration of the session or forever. (Or reload it every
single time
s that IE5 (and perhaps other browsers and versions)
but NOT Netscape 4.x have absolutely no respect for cache-control.
But IE5 still caches the damn things! Does anyone have a suggestion?
Please note that I don't have the ability to modify the IMG SRC
dynamically since the HTML resides on our customers'
L allowing the user to select their look
of choice.
The problem I have is that IE5 (and perhaps other browsers and versions)
but NOT Netscape 4.x have absolutely no respect for cache-control.
My code does this:
$r-no_cache(1);
# some code to calculate a date 10 years ago (!) goes here.
On Fri, 26 May 2000, Nick Tonkin wrote:
In our experience the only thing that guarantees no cacheing is returning
302. Also appending a query string (even an empty one) to the redirect URI
seems to make it even more solid.
So in your script you would build up your destination URI, append
