perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Faust" <cfa...@doyougot.com>
Subject Re: HTTP headers - what is wrong
Date Fri, 30 Jul 2004 09:41:15 GMT
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" <jhiver@mkdoc.com>
To: "Chris Faust" <cfaust@doyougot.com>
Cc: <modperl@perl.apache.org>
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


Mime
View raw message