Question

We have an app running on a Facebook tab at the moment which is receiving a good deal of traffic. People are signing up every few seconds, and most are successful. However I am running into the following problems:

– access token not received at all (empty response, no error)

– or if it is received, then API call to /me fails (empty response, no error)

EDIT: Apparently limiting of API calls is not the issue, since the 600/600 calls/sec is per user which makes a lot more sense :).

Is anyone else experiencing such issues? I am getting about 20-30 successful app signups a minute and about 2-3 failing ones. Note: these are not users who deny access to the app – those are handled elsewhere…

EDIT: I am getting “failed to open stream: HTTP request failed! HTTP/1.0 400 Bad Request”

$token_url = "https://graph.facebook.com/oauth/access_token?client_id=".$oauth_clientid."&redirect_uri=".urlencode($redirect_url)."&client_secret=".$oauth_secret."&code=".$code;
$access_token = file_get_contents($token_url);

Answer 1

Update: After modifying my code to use curl, there was some improvement, but it did not resolve the issue. The application in question is now past its peak usage, so obviously the number of errors have gone down drastically. It still happens sometimes. The errors are (most often):

• Curl error (6): Couldn’t resolve host ‘graph.facebook.com’
• Curl error (28): SSL connection timeout

…and other similar errors.

From my experience with a week or two of data, it seems to effect about a percent of requests when there is high traffic, less when there is low – but this is quite unscientific. 🙂

—

So the solution? Well there is none really. It seems that some percent of requests will fail and my (your) application needs to handle these errors as elegantly as possible.

My only question is, has anyone else had such experience with high traffic apps? (meaning in this case 100 000-500 000 daily pageviews and 50 000-100 000 active users)