H Ryan, Thanks for coming back on this. Here's a bit of logging which has the url query and the precise time of the returned search, the timezone is Europe/London. The ip is 67.23.28.168. I might be able to get more for other times, let me know if you need 'em. This app is in development so it may yet be some bug with me. Ben
DEBUG - urlopen success on http://search.twitter.com/search.json?q=this&rpp=100&geocode=51.51076%2C-0.13126%2C23mi&since_id=3561793228 , code 200 2009-08-26 19:55:01,783 - twittersearch.models - DEBUG - search answer: 2009-08-26 19:55:01,783 - twittersearch.models - CRITICAL - Search did not reutrn a json object! code = 200 answer = <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/strict.dtd ">^M 2009-08-26 20:10:02,548 - twittersearch.models - DEBUG - urlopen success on http://search.twitter.com/search.json?q=this&rpp=100&geocode=51.51076%2C-0.13126%2C23mi&since_id=3561793228 , code 200 2009-08-26 20:10:02,548 - twittersearch.models - DEBUG - search answer: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/strict.dtd ">^M 2009-08-26 20:25:02,439 - twittersearch.models - DEBUG - urlopen success on http://search.twitter.com/search.json?q=this&rpp=100&geocode=51.51076%2C-0.13126%2C23mi&since_id=3561793228 , code 200 2009-08-26 20:25:02,439 - twittersearch.models - DEBUG - search answer: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/strict.dtd ">^M 2009-08-26 20:25:02,439 - twittersearch.models - CRITICAL - Search did not reutrn a json object! code = 200 answer = <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.or 2009-08-26 20:40:07,334 - twittersearch.models - DEBUG - urlopen success on http://search.twitter.com/search.json?q=this&rpp=100&geocode=51.51076%2C-0.13126%2C23mi&since_id=3561793228 , code 200 2009-08-26 20:40:07,334 - twittersearch.models - DEBUG - search answer: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/strict.dtd ">^M 2009-08-26 20:40:07,334 - twittersearch.models - CRITICAL - Search did not reutrn a json object! code = 200 answer = <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.or The response is always: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/strict.dtd "> <!-- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd";> --> <HTML> <HEAD> <META HTTP-EQUIV="Refresh" CONTENT="0.1"> <META HTTP-EQUIV="Pragma" CONTENT="no-cache"> <META HTTP-EQUIV="Expires" CONTENT="-1"> <TITLE></TITLE> </HEAD> <BODY><P></BODY> </HTML> On 26 Aug 2009, at 17:27, 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, Ryan > > On Wed, Aug 26, 2009 at 7:00 AM, ben<ben.apperr...@googlemail.com> > 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: >> >> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/ >> TR/1999/REC-html401-19991224/strict.dtd"> >> <!-- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" >> "http://www.w3.org/TR/html4/strict.dtd";> --> >> <HTML> >> <HEAD> >> <META HTTP-EQUIV="Refresh" CONTENT="0.1"> >> <META HTTP-EQUIV="Pragma" CONTENT="no-cache"> >> <META HTTP-EQUIV="Expires" CONTENT="-1"> >> <TITLE></TITLE> >> </HEAD> >> <BODY><P></BODY> >> </HTML> >> >> Does anyone recognise what this kind of response means? Is it normal, >> or just beta-ish quirks? >>
