Re: Preventing data from being reposted?
| From: | rory walsh | Date: | Thu, 03 Mar 2005 15:47:05 +0000 |
| Subject: | Re: Preventing data from being reposted? | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-209927@lists.php.net to get a copy of this message | ||
Cheers, yeah closing and opening the browser was something that I didn't work out straight away, that was frustrating, I'll check out your headers, thanks again for the help,
Rory.
Jochem Maas wrote:
rory walsh wrote:I'm pretty sure I am looking at cached pages but the problem with this seems to be that some browsers support these header directives and others don't, i.e. Firefox. The following work in IE but not Firefox header("Cache-control: private"); header("Cache-Control: no-store, no-cache, must-revalidate");I'd guess that should work but maybe the 'private' throws firefox a curveball, anyway here are the headers I use to 'privatise' logged in sessions:header("Expires: ".gmdate("D, d M Y H:i:s", strtotime('1-Jan-1980')) . " GMT"); // always modified header("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT"); // HTTP/1.1 header("Cache-Control: no-store, no-cache, must-revalidate"); header("Cache-Control: post-check=0, pre-check=0", false); // HTTP/1.0 header("Pragma: no-cache");