I am working on a Facebook app and there is something I understand how their authorization system works.
Our basic setup is
canvas URL = domain.com/facebook
This is a simple page that contains FBML IFAM element which is the domain / Facebook / App, which is an HTML page that works for a flash application
The Flash application requests additional data from our application server - some of them requested Facebook data (like Friend ID List).
Then Flash again makes a request Domain.com/resources/facebook/friends - this is a PHP page that creates a Facebook instance (their PHP library) and makes the calls required by your API and Gives data.
However, the request is not valid by this URL (by Flash), so after that it is redirected to your login, when it has two parameters - auth_token and Next < / Strong> will redirect your canvas URL back to. The request is valid, but the redirect breaks the flash call.
So, I'm trying to figure out how to make these other API calls (when they call themselves Facebook APIs).
OK, I thought it.
It has been found that Flash already follows redirects - when I was noticed with the presence of an authorization request ( auth_token and next and include auth_token as a GET parameter when I forward the URL (originally forwarded to auth_token on the original request) I'm redirected to
Therefore, I said above the opposite, the redirect does not break the flash call - it was not enough data to be a legitimate request.
Comments
Post a Comment