|
|
Posted by -Lost on 03/29/07 15:32
"Steve" <no.one@example.com> wrote in message news:4PQOh.20$Ai4.7@newsfe06.lga...
>
> "-Lost" <missed-spam@comcast.net> wrote in message
> news:-_CdnfFdUfW8WpbbnZ2dnUVZ_silnZ2d@comcast.com...
> |I have tried the defacto:
> |
> | header("Cache-Control: no-cache, must-revalidate"); // HTTP/1.1
> | header("Expires: Mon, 26 Jul 1997 05:00:00 GMT"); // Date in the past
> |
> | ...but Firefox keeps on caching results form a POST'd form.
> |
> | Anyone know of any tricks or other headers to send to tame Firefox's
> cache?
>
> there is NO guarantee that ANYTHING you do will have an effect on the
> browser. that's just the way it is.
Of course. I just thought there might be some existing known kludges.
> you should also set pragma params and
> put meta-pragma directives at the top AND bottom of your html.
Placing meta information at the bottom? Before the BODY I imagine? Is that valid?
> microsoft had
> a whole long write-up on that one b/c their own browser didn't behave as web
> designers thought it should - they of course offered their explanation of
> why things were/are the way they were/are...but, at least they gave that as
> a plausible solution.
Thanks. Does that write-up exist still, or no?
> btw, how do you KNOW ff is caching?
It continuously takes a refresh or two (of the form page) before I get my POST'd results
to display the updated value. I figure it had to be Firefox as the PHP context simply
dumps the contents of $_POST. If my variable was continually in error, it must have been
Firefox sending it right?
Or some combination of me not setting the correct headers, assuming there are any that
will make a difference.
http://us3.php.net/manual/en/function.header.php#72652
Led me to believe it might actually be an Apache issue. I did however try using
MultiViews as "guesswho" suggested to no avail. I am not familiar with any other content
negotiation mechanisms of Apache.
*shrugs*
-Lost
Navigation:
[Reply to this message]
|