How do I avoid Facebook adding _escaped_fragment_ to urls in Facebook comments notifications? -
i have angular site uses hashbang (#!) in urls. render these pages crawlers , facebook bot (who changes #! ?_escaped_fragment) have server side logic add meta-tags, open graph tags etc , render special version of page.
i.e: http://example.com/something/#!/a/special/url fetched facebook using http://example.com/something/?_escaped_fragment_=/a/special/url , server responds correctly.
this works great. facebook's own open graph debug page fetches page meta data correctly. , able share page on facebook.
but pages have facebook comments. added javascript inserts
<div class="fb-comments fb_iframe_widget fb_iframe_widget_fluid" data-href="http://example.com/something/#!/a/special/url" data-numposts="5" data-width="100%" data-version="v2.3" data-colorscheme="light" </div>
the comment box shown , good. can post comments , see them later.
but: when facebook sends notifications other users have commented, link displayed on facebook has ?_escaped_fragment_ , not hashbang (#!) resulting in user getting "special" facebook page. strange me since escaped fragment supposed used bots, not when displayed in links.
the link on facebook notifications on format lsr.php?u=http%3a%2f%2fexample.com%2fsomething%2f%3f_escaped_fragment_%3d%a%252fspecial%252furl%252f17%252f&ext=......
is there way avoid facebook displaying _escaped_fragment_ when displaying link?
Comments
Post a Comment