Created By
Joel Mello
11/07/2012 4:59pm

Subscribers (17)

Bugs11/07/2012 Graph API search periocially returning empty results

  • Status: Duplicate
  • Priority: None
  • Updated: November 9, 2012 at 10:57am
Latest response from Facebook
Sean Quinlan
We are already tracking this issue in another bug report. Thanks.
Marked as Duplicate of open graph api search returning no data/posts · November 9, 2012 at 10:57am
Graph API will periodically returning empty results consistently for a long period of time (30 mins-1hr typically, if not longer). We experienced this issue yesterday from 6pm to 6:40pm and today from 4:30pm to 5:00pm. When it fails, it will fail for all browser requests from our dev box network (24.x.x.x) as well as all requests from our office network (71.x.x.x). At the moment, while it fails consistently for our dev boxes and local boxes (different outgoing IPs), it is working properly for our production server (184.x.x.x) and someone's home machine (71.x.x.x).

It feels like IP based rate limiting, except 1) we are getting back a 200 response rather than a 400/500 code and 2) We do not abuse the network and only make a handful of requests per hour with our dev machines. We've tried with and without access_token appended without any luck. After trying 20-30 times, I got a result set, then another set of 50-100 failures. This is a duplicate of my self-closed ticket http://developers.facebook.com/bugs/365863743505525?browse=search_509b01263878a9452559953

Fiddler results from now:


Fiddler results from last bug ticket:

Request:

GET http://graph.facebook.com/search?q=test HTTP/1.1
Host: graph.facebook.com
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3


Response:

HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Cache-Control: private, no-cache, no-store, must-revalidate
Content-Type: text/javascript; charset=UTF-8
ETag: "cacca674ed49d64124f812372ad595613d0d90b3"
Expires: Sat, 01 Jan 2000 00:00:00 GMT
P3P: CP="Facebook does not have a P3P policy. Learn why here: http://fb.me/p3p"
Pragma: no-cache
X-FB-Rev: 665811
Set-Cookie: _e_0ikB_0=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/; domain=.facebook.com; httponly
Set-Cookie: _e_0ikB_1=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/; domain=.facebook.com; httponly
Set-Cookie: _e_0ikB_2=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/; domain=.facebook.com; httponly
Set-Cookie: _e_0ikB_3=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/; domain=.facebook.com; httponly
Set-Cookie: wd=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/; domain=.facebook.com; httponly
X-FB-Debug: Ob3w1KgweaiQ573GyNeu6oJqzguHcxvjFPLh92sUhDc=
Date: Wed, 07 Nov 2012 02:30:08 GMT
Connection: keep-alive
Content-Length: 28

{
"data": [

]
}
6 people can reproduce this issue by following these steps
Repro