https://www.facebook.com/dialog/oauth?client_id=YOUR_APP_ID&redirect_uri=YOUR_URL?orig_url=http://example.com/default.aspx
Of course you would url encode the orig_url parameter and then decode it when you wanted to use it... it actually does work for the above type of call... but when calling the app authentication api it doesn't like it. Base64 encoding it doesn't work either. And remember, a little known fact is that the redirect_uri needs to be the same for when you are doing the app authorization as the app authentication (see below url)
https://graph.facebook.com/oauth/access_token?client_id=YOUR_APP_ID&redirect_uri
=YOUR_URL?orig_url=http://example.com/default.aspx&client_secret=YOUR_APP_SECRET&code=THE_CODE_FROM_ABOVE
Bottom line is that I tried the above approaches and kept getting a HTTP 400 error "Error validating verification code.".
SOLUTION: Taking a step back, rather than try and get what should work working, try a different approach. In my case, simply put the original URL into a session variable for use later on (http://stackoverflow.com/questions/5747320/how-to-encode-the-redirect-uri-for-facebook-login).
e.g.
Session["UrlToReturnToAfterLogin"] = HttpContext.Current.Request.Url.OriginalString;
Too easy.
The Facebook Graph API's flexibility shines through its redirect_uri and QueryString parameters, granting developers precision and customization. These features empower seamless navigation and data retrieval, allowing for tailored user experiences. The redirect_uri refines user journeys by guiding them post-authorization, while QueryString parameters facilitate targeted data requests. This level of control and specificity ensures efficient data handling, enabling apps to fetch and utilize information precisely as needed. Facebook API attention to detail with these parameters underscores its commitment to developer empowerment and user-centric functionality.
ReplyDelete