title: Response.Redirect with a fragment identifier causes unexpected refresh when later using location.hash
body: <p>I was hoping someone can assist in describing a workaround solution to the following issue I am running into on my ASP.NET website on IE. In the following I will describe the bug and clarify the requirements of the needed solution.</p>
  
  <p><strong>Repro Steps:</strong></p>
  
  <ol>
  <li>User visits A.aspx</li>
  <li>A.aspx uses Response.Redirect to bring the user to B.aspx#house</li>
  <li>On B.aspx#house, the user clicks a button that sets window.location.hash='test'</li>
  </ol>
  
  <p><strong>Actual Results:</strong></p>
  
  <p>B.aspx is loaded again. The URL now shows B.aspx#test</p>
  
  <p><strong>Expected Results:</strong></p>
  
  <p>No reload. The URL will just change to B.aspx#test</p>
  
  <p><strong>Requirements:</strong></p>
  
  <ol>
  <li>Page A must redirect to page B with a fragment identifier in the url</li>
  <li>Any user action on page B will set the location.hash</li>
  <li>Setting location.hash must not make page B refresh</li>
  <li>This must work on IE</li>
  </ol>
  
  <p><strong>Notes:</strong></p>
  
  <ol>
  <li>Bug only repros on IE (tested on ie6|7|8). Opera, FF, Chrome, Safari all have the expected results of no reload.</li>
  <li>This error may have nothing to do with ASP.NET, and everything to do with IE</li>
  <li>For any kind soul willing to have a look at this, I have created a minimal ASP.NET web project to make it easy to repro <a href="http://www.4shared.com/file/185276862/2e873594/ReproRedirectHashRefreshBug.html" rel="nofollow noreferrer">here</a></li>
  </ol>