Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You can <em>only</em> get rid of this client-side.</p> <p>You might think that you could solve this server-side by redirecting to a URL without the anchor:</p> <ul> <li>facebook redirects to <code>http://MyFacebookRedirectUrl...#_=_</code></li> <li>Then we redirect to some new URL, without the anchor</li> </ul> <p>....But the <code>#_=_</code> reappears by magic in the browser address bar - how?</p> <p>See James Pearce's answer at <a href="http://developers.facebook.com/bugs/318390728250352" rel="nofollow">http://developers.facebook.com/bugs/318390728250352</a> :</p> <p><em>"Some browsers will append the hash fragment from a URL to the end of a new URL to which they have been redirected (if that new URL does not itself have a hash fragment)."</em></p> <p>and also this:</p> <p><a href="http://blogs.msdn.com/b/ieinternals/archive/2011/05/17/url-fragments-and-redirects-anchor-hash-missing.aspx" rel="nofollow">http://blogs.msdn.com/b/ieinternals/archive/2011/05/17/url-fragments-and-redirects-anchor-hash-missing.aspx</a></p> <blockquote> <p>Firefox, Chrome, and Opera [and now IE10] will re-attach a URL Fragment after a HTTP/3xx redirection has taken place, even though that fragment was not present in the URL specified by the Location header on the redirection response</p> </blockquote> <p>So if you're just doing server side redirects from your Facebook redirect page, you're going to have to remove this client-side.</p> <p>The other alternative is to redirect server-side to a URL that contains a different named anchor - but that doesn't really solve the problem and not all browsers will do the same thing.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload