Thanks Fred, that did the trick...
-Chris
- Original Message -
From: [EMAIL PROTECTED]
To: Chris Faust [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, July 27, 2004 12:02 PM
Subject: Re: HTTP headers - what is wrong
Which works great, the problem is right before I print out
Chris Faust wrote:
What would you suggest for a situation where a user is entering in their
credit card information, using their back button and submitting again and
then complaining about a double charge?
I would suggest that you need to create some kind of transaction ticket.
For example,
Folks,
I need to expire a page so if a user uses his back
button, he will not be able to the previous page (which as a form
etc.)..
On perl.apache.org I found
$r-no_cache(1);
Which works great, the problem is right before I
print out any HTML, I changed
$CGI-header
to
Which works great, the problem is right before I print out any HTML, I
changed
$CGI-header
to $r-send_http_header;
The method $r-send_http_header() no longer exists in mod_perl 2.0.
See the following link
Chris Faust wrote:
Folks,
I need to expire a page so if a user uses his back button, he will not
be able to the previous page (which as a form etc.)..
Sorry if this sounds troll-ish, but IMHO if your application is designed
in such a way that you need to sacrifice standard browser
