Server.Transfer Refreshing Browser Problem

[Ian Walsh]

I have two pages in my project.

Page 1 has a command button that when it is clicked inserts a record
in a database and does a server.transfer to Page2.

The problem is, if I do a refresh when the browser gets to Page2, it
re-runs the insert code on Page1 resulting in two records being
inserted. I guess the whole point of Server.Transfer is that it all
happens server side.

I like using Server.Transfer, because I don't have to have query
strings and session variables obviously span the whole project. Is
there any way to stop this behaviour?

 

[Richard K Bethell]

I have two pages in my project.

Page 1 has a command button that when it is clicked inserts a record
in a database and does a server.transfer to Page2.

The problem is, if I do a refresh when the browser gets to Page2, it
re-runs the insert code on Page1 resulting in two records being
inserted. I guess the whole point of Server.Transfer is that it all
happens server side.

I like using Server.Transfer, because I don't have to have query
strings and session variables obviously span the whole project. Is
there any way to stop this behaviour?

Not really. Your browser still thinks it is at the old page, and is hitting
up the old page with a new request. F5 IE refreshes are very dangerous in
this context. The one nice thing about Response.Redirect() is that, despite
the round tripping, there is no risk of this sort of thing happening.

R.