Error refreshing a web page

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Something happened to my development environment and I'm getting an error
that hasn't happened before. Not knowing why the error is popping up is
preventing me from figuring out what in my environment changed.

Environment: VS 2005 team developer, AJAX extensions, .NET 2.0.

Here's how I generate the error:

1. Create a new web site.
2. Drop a button on the default page.
3. Double-click the button to generate a handler.
4. Build the solution.
5. Run the web site in the debugger.

The browser's refresh button works fine UNTIL I click the button on the
page. From that point on, clicking the button still works fine, but the
refresh button pops up a Windows Internet Explorer warning dialog that
contains the text

"To display the webpage again, Internet Explorer needs to resend the
information you've previously submitted.

If you were making a purchase, you should click the Cancel to avoid a
duplicate transaction. Otherwise, clidck Retry to display the webpage again."

along with a Retry and Cancel button. Neither button seems to change this
popup on subsequent attempts to refresh the page.

Things I've done recently that might have affected the environment:

1. Installed Expression Web trial
2. Installed VS Orcas trial

I've uninstalled Expression Web, Orcas, and the .NET 3.0 and 3.5 that Orcas
added for me.

What is going on? I suspect that this error isn't real. When this warning
dialog pops up, what information is IE trying to send to the server that it
thinks it hasn't yet managed to send successfully? If this is really an
error, what is preventing IE from realizing that it completed the last page
update successfully? Trace output looks correct in terms of execution
sequence and I can stop on breakpoints in the Page_Load and Button1_Click
functions. How do I get rid of this problem and restore my development
environment?

HELP!
 
this is browser normal behavior. if the current page is a result of a
postback (button clicked rather than a hyperlink), then to do a refresh
the browser needs to post the data again (rerunning the page logic).
because so many sites failed to handle this on their purchase page, the
browsers had to add this message to prevent double buys.


-- bruce (sqlwork.com)
 
since my work has nothing to do with commerce, how do i suppress the
behavior? what is the behind-the-covers mechanism that is invoking it so
that i can figure out why and how it's doing what it does?

i think it's odd to say the least that a simple post-back procedure causes a
browser to pop up such a specific message, especially if the browser cannot
have any knowledge that the user is actually performing a commercial
transactions of some sort.

i've been working through asp.net 2.0 examples with post-back functions for
several weeks, and this is the first time i've seen the behavior. this leads
me to think that it's not normal. has IE been changed recently to add this
popup?

james
 
Browser displays that message only if page is result of submitting form with
method POST. Which is how any buttom works in .NET
you can get away with that if any action (i.e. button click) you will end
with Response.Redirect somewere. Then it will me method "GET".

George.
 
Back
Top