I had the same problem when i tried to disable cache through mod_perl2
own modules. In my case the Cache-Control headers solution pointed
here was not sufficient.
I followed the http headers through the firefox popular extension and
what i saw was that the important "tags" the browser was looking a
Thanks for your answer Nick,
i still don't understand what mod_expires stand for, but anyway i solved
my problem sending custom "no-cache" headers thanks to mod_headers, and
i work like a charm :
Header set Expires "Thu, 01 Dec 2003 16:00:00 GMT"
Header set Cache-Control "no-store, no-cache,
On Monday 21 November 2005 11:36, gregory duchesnes wrote:
> Therefore i didn't understand what mod_expires does!?
>
> That mechanism i correct in case i don't use mod_expires, but i want to
> invalidate cache as soon as the client gets the file.
You can invalidate the cache as much as you like (I
Therefore i didn't understand what mod_expires does!?
That mechanism i correct in case i don't use mod_expires, but i want to
invalidate cache as soon as the client gets the file.
Did i misread mod_expires documentation? What mod_expires is used for then?
Nick Kew a écrit :
On Monday 21 Nove
On Monday 21 November 2005 11:20, gregory duchesnes wrote:
> But it does not change anything, my browser (Firefox 1.0.7) first get
> the file normally from the server, but if i close the browser and try
> and grab the file again, i get a HTTP 304 not modified code instead of
> the HTTP 200 code i
I all,
i'm trying to make mod_expires work on my server (Debian stable).
First i tried to make it work serverwide (just for testing) I then added
those two lines in my main conf file :
ExpiresActive On
ExpiresDefault "now plus 1 seconds"
# i also tried this
ExpiresDefault A1
But it does not
