Either way an XML or JSON feed should NEVER return HTML!

On Sep 7, 11:25 am, Ben Eliott <ben.apperr...@googlemail.com> wrote:
> IP: 67.23.28.168, time is Europe/London
>
> 2009-09-07 11:19:48,014 - 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
> ">
> <!-- <!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>
>
> Starting to wonder whether this is connected to auth/user agent.
>
> On 6 Sep 2009, at 20:35, Rudifa wrote:
>
>
>
> > I have seen this same http page with empty body
> > <!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>
> > 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 <iamthebisc...@gmail.com> wrote:
> >> I'm consistently getting the same response when 
> >> accessinghttp://search.twitter.com/trends.jsonfrom
> >>  209.40.204.183
>
> >> Steve
>
> >> On Aug 26, 5:27 pm, Ryan Sarver <rsar...@twitter.com> 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<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?

Reply via email to