<div>
I am afraid you're going to have to post code from pages where the error occurs. The code from the previous page and current.
</div>


<div>
No error occurs... what happens is you are on page A. Then you click a link which takes you to page B. If you click BACK it goes back to page A, fine. BUT if you are sitting on page B and then click another link that takes you to page C, when you click BACK it goes back to page B but you can nolonger click BACK to get to page A, it is GONE. So my BACK functionality is only remembering one page back. See code:<br />
<br />

<pre><code class="code-1 nolinks" id="code-424618"><span>In the Page Load event:</span>
<span> </span>
<span>        TopBackButton.Attributes(&quot;onclick&quot;) = &quot;history.back();return false</span>
</code></pre>
</div>


<div>
This problem is really embarassing for us. All our customers are complaining that it does nort always work. Any one have any ideas? It used to work fine prior to IE8 being released. Thanks.
</div>


<div>
Are you implementing any ajax? using response.Redirect?
</div>


<div>
I am &nbsp;NOT using Ajax. I am definitely using response.redirect all over the place.<br />

</div>


<div>
That could cause it.<br />
If you go from page A to page B using Response.Redirect that could cause the issue because Response.Redirect tells the client that page A has temporarily moved to page B, without saying it for certain it could cause the back button to glitch in IE8. I can't be certain, try to make a test and remove the response.Redirect and use a regular link.
</div>


<div>
What do you mean by a regular link. I mean I know about &lt;a href= etc,,, but when certain buttons are clicked I need to handle the click event, perform some sub-routines and then reponse.redirect. How do I redirect to a new page with a query string in my code behind without using response.redirect?<br />
Thanks<br />

</div>


<div>
You don't. Like I said this is for testing purposes only. Remove the functionality and place a normal anchor tag to go from page A to B to C. If that works then it's likely that Response.Redirect is the culprit.
</div>


<div>
ok. Lets say that response.redirect is the culprit. What do I use instead? I can't be the only one who has written an ASP .Net Web Site with BACK buttons. Even the browser's own BACK button icon gets greyed out after the 1st BACK step. This should be an easy one I think. Do most developers NOT use response.redirect? Is their a known issue with that? Sorry, but to have to test this theory with no altermative solution if the theory proves right seems like a waste of time. And I am very busy now with other pressing items. If there was a porposed altermative to using response.redirect in my scenario then I would take the time to test it knowing that if it is the culprit then follow these steps to solve....<br />
<br />
Thanks for your suggestions.<br />
Help please.<br />

</div>


<div>
I am not saying Response.Redirect is the problem. It's just a troubleshooting step. Take it out and see what happens.
</div>


<div>
You know, it works fine in Firefox and Safari, gee what a surprise (frustrated). I will have to setup a hidden test web site with pages that you get to just with &lt;a href... links to test this out. I cannot change the design of our live web site just to test theories and we only have 1 outside IP address.<br />
<br />
But I beg this question, if it is response.redirect, what do you use as an alternative? I find it hard to believe that such a common methid causes such a big problem with such a simple thing such as browser history.<br />
<br />
Any one else?<br />
&nbsp;
</div>


<div>
alternative add javascript to direct the browser to another page. However, I do not know for sure that it's Response.Redirect. First you need to confirm that. Modify the site on your development server or workstation.
</div>


<div>
In this large community of .Net developers, are others using response.redirect and not having a BACK button issue in IE8? This is utterly rediculous, works fine in Firefox and Safari. So very embarassing. &quot;Your web site BACK buttons do not always work, I hate it!&quot; are some of the comments I am getting. Unless of course they are using a real browser like Firefox or Safari, anything but IE8! I am using standard response.redirect's and &lt;a href= tags which are all legal and common. Sometimes it works, sometimes it won't. No rhime or reason.<br />
<br />
THIS BROKE AS OF IE8. NO ONE ELSE HAVING SUCH AN ISSUE AFTER USING MS VISUAL STUDIO 2005 WEB SITE PROJECT??<br />
<br />
This issue should not be such a brain teaser, simple browser history back button. <br />
<br />
Any helpful suggestions would be greatly appreciated.
</div>


<div>
There is no way you can modify the code to debug? You have no development version?
</div>


<div>
I guess I have the same question, why does it work in IE versions earlier than 8 and in current versions of Firefox and Safari? What has changed in IE8 and how do I become &quot;compatible&quot;. I mean I did use an MS product, VS2005 ASP.Net VB, to develop this web site and hence I have a problem ONLY with the latest version of MS IE8.<br />
<br />
Ebentually I will have no choice but to spend much time to try and some how debug something I suspect is not a bug on my end. <br />
<br />
Thanks for your suggestions,<br />

</div>


<div>
Well uess what? It is suddenly working normally again for me and customers that I have asked. Why you ask? THE LATEST WINDOWS UPDATES. Ever since installing the recent automatic Windows updsates this problem is resolved! <br />
<br />
So it must have been a microsoft bug, just as I suspected. All I can say is I am glad it is resolved and we do not have to look like toal idiots!<br />
<br />
End.
</div>


<div>
glad everything worked out for you.
</div>


<div>
Glad it works for you. The latest update for me on ie8 makes my response.redirect not work now.
</div>


<div>
It was never confirmed, nor do I believe, that response.redirect had anything to do with my issue. My issue was actually a browser history issue where the BACK button was not working consistently, sometimes yes and sometimes no. The latest windows updates appears to have resolved this issue. <br />
<br />
I have had a similar issue to yours (I think) where any button I click would send me to my default url (Home.aspx). This was, and still is, very frustrating. I have resolved it by un-installing all versions of the .Net framework up to and including .Net 2.0, re-install .Net Framework 2.0 and then 2.0 SP1 BUT STOP THERE! Do NOT install 2.0 SP2 or the same problem recurrs.<br />
<br />
Hope this helps.<br />
&nbsp;
</div>


<div>
<div class="content wysiwyg-content">
I recently completed and launched an ASP.Net web site while IE7 was the standard, Ever since IE8 both we and our users have problems trying to use the BACK button which used to work just fine. In IE8 some times it works and some times it don't! Why? How do I resolve this? I already know about the need for clicking on compatability view so the layout is not screwed but how to get the BACK button to do what it is supposed to do consistently, just like it always used to. Thanks again Microsoft! :(<br />
Oh, why not, if any one knows why we suddenly have to click compatability view and how to resolve it so we do not have to I would also appreciate it. I guess MS has nothing better to do than break things that worked just fine to begin with. Thanks, 
</div>
</div>


I recently completed and launched an ASP.Net web site while IE7 was the standard, Ever since IE8 both we and our users have problems trying to use the BACK button which used to work just fine. In IE8 some times it works and some times it don't! Why? How do I resolve this? I already know about the need for clicking on compatability view so the layout is not screwed but how to get the BACK button to do what it is supposed to do consistently, just like it always used to. Thanks again Microsoft! :(
Oh, why not, if any one knows why we suddenly have to click compatability view and how to resolve it so we do not have to I would also appreciate it. I guess MS has nothing better to do than break things that worked just fine to begin with. Thanks, 

IE8 BACK button broken

Web browsers are applications used primarily to display documents, files and media from the Internet, identified by a Uniform Resource Identifier (URI) that can be a page, image, video or other file. Some browsers require the use of add-ons or extensions to safely render the information they receive; others have systems built into them to perform the same functions.

Web Browsers

The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications