469,601 Members | 2,039 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,601 developers. It's quick & easy.

How to handle form double submitting.


This may sound like a silly question, but what is the appropriate way to
handle form double submitting in ASP.NET. Page expiration, etc? I am
looking for a way to handle this in some cetral point of the application
without affecting the web page implementation.

Thanks,
Nacho
Nov 19 '05 #1
4 1498
There's actually a new gadget from thinkgeek.com that installs as an ActiveX
component into your webpage that once they click the submit button it reaches
out and dismembers the user's primary index finger. It works like a charm ;)

Seriously, though, the best two approaches I've seen are 1) Education. Teach
people that this is how the infrastructure works. Let them know they'll be
charged twice on their creditcard or they'll do the transfer of funds twice.
Failing that 2) Use javascript to disable or hide the submit button upon
clicking it.

-Brock
DevelopMentor
http://staff.develop.com/ballen
This may sound like a silly question, but what is the appropriate way
to handle form double submitting in ASP.NET. Page expiration, etc? I
am looking for a way to handle this in some cetral point of the
application without affecting the web page implementation.

Thanks,
Nacho


Nov 19 '05 #2
Maybe thinkgeek.com need to implement this for Mozilla too ;)

Back to the problem, I thought about such approaches, but it's very
important to resolve the problem back on the server-side. I will not sleep
well if I rely on the browser for this and also it does not secures the
app from replay attacks.

/Nacho
On Fri, 08 Apr 2005 05:36:28 -0700, Brock Allen <ba****@NOSPAMdevelop.com>
wrote:
There's actually a new gadget from thinkgeek.com that installs as an
ActiveX component into your webpage that once they click the submit
button it reaches out and dismembers the user's primary index finger. It
works like a charm ;)

Seriously, though, the best two approaches I've seen are 1) Education.
Teach people that this is how the infrastructure works. Let them know
they'll be charged twice on their creditcard or they'll do the transfer
of funds twice. Failing that 2) Use javascript to disable or hide the
submit button upon clicking it.

-Brock
DevelopMentor
http://staff.develop.com/ballen
This may sound like a silly question, but what is the appropriate way
to handle form double submitting in ASP.NET. Page expiration, etc? I
am looking for a way to handle this in some cetral point of the
application without affecting the web page implementation.
Thanks,
Nacho


Nov 19 '05 #3
Does IE not have an option to detect accidental double clicks or is that
Windows Explorer, I forget :S

MattC

"Nacho Nachev" <do**@spam.me> wrote in message
news:op**************@nnachev.sofia.wizcom.bg...
Maybe thinkgeek.com need to implement this for Mozilla too ;)

Back to the problem, I thought about such approaches, but it's very
important to resolve the problem back on the server-side. I will not sleep
well if I rely on the browser for this and also it does not secures the
app from replay attacks.

/Nacho
On Fri, 08 Apr 2005 05:36:28 -0700, Brock Allen <ba****@NOSPAMdevelop.com>
wrote:
There's actually a new gadget from thinkgeek.com that installs as an
ActiveX component into your webpage that once they click the submit
button it reaches out and dismembers the user's primary index finger. It
works like a charm ;)

Seriously, though, the best two approaches I've seen are 1) Education.
Teach people that this is how the infrastructure works. Let them know
they'll be charged twice on their creditcard or they'll do the transfer
of funds twice. Failing that 2) Use javascript to disable or hide the
submit button upon clicking it.

-Brock
DevelopMentor
http://staff.develop.com/ballen
This may sound like a silly question, but what is the appropriate way
to handle form double submitting in ASP.NET. Page expiration, etc? I
am looking for a way to handle this in some cetral point of the
application without affecting the web page implementation.
Thanks,
Nacho


Nov 19 '05 #4
Then the only other thing is to track the last time the user posted to the
page. You could even make it more elaborate and track it based upon the values
in the form. In any event, it will be something you build yourself unless
you can find something that already does this.

-Brock
DevelopMentor
http://staff.develop.com/ballen
Maybe thinkgeek.com need to implement this for Mozilla too ;)

Back to the problem, I thought about such approaches, but it's very
important to resolve the problem back on the server-side. I will not
sleep well if I rely on the browser for this and also it does not
secures the app from replay attacks.

/Nacho

On Fri, 08 Apr 2005 05:36:28 -0700, Brock Allen
<ba****@NOSPAMdevelop.com> wrote:
There's actually a new gadget from thinkgeek.com that installs as an
ActiveX component into your webpage that once they click the submit
button it reaches out and dismembers the user's primary index finger.
It works like a charm ;)

Seriously, though, the best two approaches I've seen are 1)
Education. Teach people that this is how the infrastructure works.
Let them know they'll be charged twice on their creditcard or
they'll do the transfer of funds twice. Failing that 2) Use
javascript to disable or hide the submit button upon clicking it.

-Brock
DevelopMentor
http://staff.develop.com/ballen
This may sound like a silly question, but what is the appropriate
way
to handle form double submitting in ASP.NET. Page expiration, etc?
I
am looking for a way to handle this in some cetral point of the
application without affecting the web page implementation.
Thanks,
Nacho


Nov 19 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Display Name | last post: by
4 posts views Thread by Altramagnus | last post: by
17 posts views Thread by axlq | last post: by
4 posts views Thread by guiromero | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.