Also, if the KB article Steven suggests doesn't help you:
The actual cause is that your output is being seen as non-buffered data by
the browser. Thus, the response contains two packets of resulting data, the
first being a 302 Object Moved HTTP response. IE gets the first packet and
starts to redirect (correctly based on the HTTP header) and then receives
the second packet and stops the redirect, hence the moved message.
A workaround is to add an ihttpmodule to the chain that adds a html meta
refresh instead of using a response.redirect to the actual page output, thus
the browser actually receives the completed output terminated with a
response.end and on receiving the completed stream correctly moves to the
new page. This should work for all IE instances.
--
Regards
John Timney
Microsoft Regional Director
Microsoft MVP
"Steven Cheng[MSFT]" <v-******@online.microsoft.com> wrote in message
news:F6*************@cpmsftngxa10.phx.gbl...
Hi Brad,
Yes, the kb article is provided for IE4, 5, but based on my research,
there seems has some former issues dicussing on the same problem and the IE
version is 6. So I think you can have a try on the workarounds in the kb
article or even try requesting the hotfix mentioned in it. Thanks.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx