Force ASP code to run entirely, regardless if reload or stop button is hit.

[grant.griffith]

I need to find a way to force all the asp code on a web page to load
regardless if the user hits the reload or stop button on the browser.
I am seeing where more and more users are doing this and it is causing
me some problems on some pages. I would guess there is a way to do
this I am just searching for the wrong thing?

 

[Patrice]

AFAIK an ASP page is always executed in its entirety (the server doesn't
know that the stop button has been clicked).

You may want to explain the problem you have so that someone could perhaps
figure the exact cause (which is likely not that). Could it be rather that
the code runs twice (for example if the user "double click" a submit button
?)

 

[grant.griffith]

My issue is on an e-commerce site where I process a transaction and
that transaction gets processed, but the email at the end of the asp
file is never sent out. Usually the user ends up with a duplicate
charge as the transaction gets processed twice but the email
confirmation only gets sent once.

 

[Evertjan.]

(e-mail address removed) wrote on 08 feb 2006 in
microsoft.public.inetserver.asp.general:

My issue is on an e-commerce site where I process a transaction and
that transaction gets processed, but the email at the end of the asp
file is never sent out. Usually the user ends up with a duplicate
charge as the transaction gets processed twice but the email
confirmation only gets sent once.

Please quote what you are replying to.

If you want to post a followup via groups.google.com, don't use the
"Reply" link at the bottom of the article. Click on "show options" at the
top of the article, then click on the "Reply" at the bottom of the article
headers.
<http://www.safalra.com/special/googlegroupsreply/>

 

[Patrice]

The page just asks the SMTP server to send the mail and continues to run
(ie. the control flow continues as soon as the request to the STMTP server
is done, not once the SMTP server has really sent the mail).

So it's likely a problem on the SMTP server side. I would check the log or
the appropriate directories to get some information on those bad mails...