HTTP request

I need some basic insight into the workings of a HTTP request and a
HTTP response. i'am using ASP.net.

1. what happens when a request is sent and the user clicks the STOP
button of the browser.
a. does the request goes through to the server?
b. will any server-side code gets executed?
c. if there is any database operations, will they get executed?

the scenario here is that, there is a online shopping site which does
credit card processing with database updates.

There is a possibility that the credit card transaction goes through
before the user hits the STOP button and the database updates does
not. The end result will be stale data! Please guide.


Thanks in advance.

Sunil.B

 > I need some basic insight into the workings of a HTTP request and a
 > HTTP response. i'am using ASP.net.

Not that we don't want to help, but the RFC is pretty simple to read, and is
always a better place to start than asking here.

 > 1. what happens when a request is sent and the user clicks the STOP
 > button of the browser.
 > a. does the request goes through to the server?

Yes.

 > b. will any server-side code gets executed?

Yes.

 > c. if there is any database operations, will they get executed?

Yes.

 > the scenario here is that, there is a online shopping site which does
 > credit card processing with database updates.

Naturally.

 > There is a possibility that the credit card transaction goes through
 > before the user hits the STOP button and the database updates does
 > not. The end result will be stale data! Please guide.

HTTP is a request/response protocol. A client sends a request, the server
responds, the client renders the data. If a request is sent to the server,
all the Stop button does is prevents the client from rendering the data that
the server returned. You can't stop a request that has been sent from being
processed by the server--all you can do is save your system the trouble of
rendering the returned data that you don't care to see.<!-- ~MESSAGE_AFTER~ -->