Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 48977 invoked from network); 30 Jul 2004 09:41:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 30 Jul 2004 09:41:44 -0000 Received: (qmail 3044 invoked by uid 500); 30 Jul 2004 09:41:34 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 2556 invoked by uid 500); 30 Jul 2004 09:41:30 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 2543 invoked by uid 99); 30 Jul 2004 09:41:30 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Message-ID: <01a901c47619$5c0bbe70$0200a8c0@analog> From: "Chris Faust" To: "Jean-Michel Hiver" Cc: References: <5ac301c473ef$94fcf400$0200a8c0@analog> <4106CEE6.30603@mkdoc.com> Subject: Re: HTTP headers - what is wrong Date: Fri, 30 Jul 2004 05:41:15 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N 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've dealt with the submit button and that took care of a lot of users that double click the thing or simply click it again as they think its taking too long - but there are still those that use the back button and refresh button, both of which causes another transaction with Versign (actually 2 as I have to fix the bad one :). I've come to find out if there is any way possible at all to cause a problem, there will be users out there that follow that exact route. -Chris ----- Original Message ----- From: "Jean-Michel Hiver" To: "Chris Faust" Cc: Sent: Tuesday, July 27, 2004 5:53 PM Subject: Re: HTTP headers - what is wrong > 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 functionality > such as the back button, then your application is very broken. > > Presumably if the user presses the back button and it doesn't work, the > next thing that will happen is that they'll close their browser and be > annoyed with your app... I don't see any reason for which you'd want to > break such a basic, important piece of standard functionality. > > http://www.google.com/search?q=usability+back+button > > Cheers, > Jean-Michel. > -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html