[twitter-dev] Re: non json response
I am able to consistently reproduce this error. I am making GET requests via PHP from IP: 96.30.16.192. I receive the error without fail after periods of inactivity lasting 2 hours or more. The header response code is 200. Please let me know if I can provide any additional info that might help you diagnose the problem, or if you have suggestions about how best to handle. Thanks. On Sep 6, 3:35 pm, Rudifa wrote: > I have seen this same http page with empty body > http://www.w3.org/ > TR/1999/REC-html401-19991224/strict.dtd"> > > > > > > > > > > > a number of times in the last few days (but intermittently - a good > response may come after several attempts), > in response tohttp://twitter.com/users/show/rudifa.json > > The most recent one was on UTC time > 2009-09-06 18:55:38.262 > My IP is 84.227.186.88 as reported byhttp://www.whatismyip.com/ > > Could someone at twitter.com please tell us what does this mean? Server > (s) overloaded? > > On Aug 30, 1:20 pm, Steven Wilkin wrote: > > > I'm consistently getting the same response when > > accessinghttp://search.twitter.com/trends.jsonfrom209.40.204.183 > > > Steve > > > On Aug 26, 5:27 pm, Ryan Sarver wrote: > > > > Ben, > > > > It's a known issue and we are trying to hunt it down. Can you please > > > provide us with your source IP and an approximate time of when you saw > > > it? > > > > Thanks, RyanOn Wed, Aug 26, 2009 at 7:00 AM, > > > ben wrote: > > > > > Occassionally i get back a 200 status html response from the json > > > > search api which look like this, most times the same search works > > > > fine, it just happens occassionally: > > > > > http://www.w3.org/ > > > > TR/1999/REC-html401-19991224/strict.dtd"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Does anyone recognise what this kind of response means? Is it normal, > > > > or just beta-ish quirks?
[twitter-dev] Re: non json response
I am able to consistently reproduce this error -- I get this response almost without fail after periods of inactivity greater than 2 hours. I am requesting XML via PHP, it's a GET request. The requests are coming from 96.30.16.192. Let me know if I can provide any additional info that might help, or if you have any suggestions about how best to handle this response. On Sep 6, 3:35 pm, Rudifa wrote: > I have seen this same http page with empty body > http://www.w3.org/ > TR/1999/REC-html401-19991224/strict.dtd"> > > > > > > > > > > > a number of times in the last few days (but intermittently - a good > response may come after several attempts), > in response tohttp://twitter.com/users/show/rudifa.json > > The most recent one was on UTC time > 2009-09-06 18:55:38.262 > My IP is 84.227.186.88 as reported byhttp://www.whatismyip.com/ > > Could someone at twitter.com please tell us what does this mean? Server > (s) overloaded? > > On Aug 30, 1:20 pm, Steven Wilkin wrote: > > > I'm consistently getting the same response when > > accessinghttp://search.twitter.com/trends.jsonfrom209.40.204.183 > > > Steve > > > On Aug 26, 5:27 pm, Ryan Sarver wrote: > > > > Ben, > > > > It's a known issue and we are trying to hunt it down. Can you please > > > provide us with your source IP and an approximate time of when you saw > > > it? > > > > Thanks, RyanOn Wed, Aug 26, 2009 at 7:00 AM, > > > ben wrote: > > > > > Occassionally i get back a 200 status html response from the json > > > > search api which look like this, most times the same search works > > > > fine, it just happens occassionally: > > > > > http://www.w3.org/ > > > > TR/1999/REC-html401-19991224/strict.dtd"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Does anyone recognise what this kind of response means? Is it normal, > > > > or just beta-ish quirks?
