Skip to main content

Facebook Callback appends "#_=_" to Return URL

Image
By User


Facebook callback has started appending #_=_ hash underscore to the Return URL



Does anyone know why? What is the solution?


Source: Tips4all, CCNA FINAL EXAM
Labels:

Comments

  1. UserMay 17, 2012 at 11:12 AM

    via Facebook's Platform Updates:


    Change in Session Redirect Behavior

    This week, we started adding a fragment #_=_ to the redirect_uri when
    this field is left blank. Please ensure that your app can handle this
    behavior.


    To prevent this, set the redirect_uri in your login url request like so: (using Facebook php-sdk)

    $facebook->getLoginUrl(array('redirect_uri' => $_SERVER['SCRIPT_URI'],'scope' => 'user_about_me'));


    UPDATE

    The above is exactly as the documentation says to fix this. However, Facebook's documented solution does not work. Please consider leaving a comment on the Facebook Platform Updates blog post and follow this bug to get a better answer. Until then, add the following to your head tag to resolve this issue:

    <script type="text/javascript">if (window.location.hash == '#_=_')window.location.hash = '';</script>

    ReplyDelete
  2. UserMay 17, 2012 at 11:12 AM

    The Facebook has a frame and inside the frame everything works with AJAX communication. The AJAX solution's biggest problem in this case to show the current state. As far I understand, the Facebook decided that they use simulated anchors. It means if you click somewhere, they simulate that this is an anchor inside the page, and when starts the AJAX communication they change your anchor bit of your URL as well.

    This solution helps you normaly, when you try to reload the page, becuase your borwser send the whole url with anchors to the facebook server / if you refresh the page (not ENTER, press F5)/. So the Facebook pick up the latest state, what you see, and able to continue there.

    When the callback returns with #_ it means nothing changed compare to basic state. Because this anchor parsed by the browser, not need to worry about it.

    ReplyDelete
  3. UserMay 17, 2012 at 11:12 AM

    Not sure why they're doing this but, you could get around this by reseting the hash at the top of your page:

    if (window.location.hash == "#_=_")
    window.location.hash = "";

    ReplyDelete
  4. UserMay 17, 2012 at 11:12 AM

    Major annoying, especially for apps that parse the URI and not just read the $_GET... Here's the hack I threw together... Enjoy!

    <html xmlns:fb='http://www.facebook.com/2008/fbml'>
    <head>
    <script type="text/javascript">
    // Get rid of the Facebook residue hash in the URI
    // Must be done in JS cuz hash only exists client-side
    // IE and Chrome version of the hack
    if (String(window.location.hash).substring(0,1) == "#") {
    window.location.hash = "";
    window.location.href=window.location.href.slice(0, -1);
    }
    // Firefox version of the hack
    if (String(location.hash).substring(0,1) == "#") {
    location.hash = "";
    location.href=location.href.substring(0,location.href.length-3);
    }
    </script>
    </head>
    <body>
    URI should be clean
    </body>
    </html>

    ReplyDelete
  5. UserMay 17, 2012 at 11:12 AM

    if you want to remove the remaining "#" from the url

    if (window.location.hash == '#_=_') {
    window.location.hash = ''; // for older browsers, leaves a # behind
    history.pushState('', document.title, window.location.pathname); // nice and clean
    e.preventDefault(); // no page reload
    }

    ReplyDelete
  6. UserMay 17, 2012 at 11:12 AM

    A change was introduced recently in how Facebook handles session redirects. See "Change in Session Redirect Behavior" in this week's Operation Developer Love blog post for the announcement.

    ReplyDelete
  7. UserMay 17, 2012 at 11:12 AM

    Adding this to my redirect page fixed the problem for me ...

    if (window.location.href.indexOf('#_=_') > 0) {
    window.location = window.location.href.replace(/#.*/, '');
    }

    ReplyDelete

Post a Comment