Hi all.

This is an extremely high priority problem for us, and for me personally, to fix.

If you're having this problem, please free to reach out to me, but please try to include:

* the IP address your request is coming from
* the request you're making
* the response you got back
* the time that the request/response was made/received

(or, a tcpdump or curl output when doing -vvv would be sufficient also)


On Sep 10, 2009, at 10:05 PM, Matthew Ranney <m...@ranney.com> wrote:

I'm seeing tons of these as well.

However, I've found that if you follow the suggestion of the META tag to simply "refresh" in 0.1 seconds if you get this bogus response, you can hide most of this from users, especially if they are on a fast network.

On Thu, Sep 10, 2009 at 2:09 PM, Monica Keller <monica.kel...@gmail.com > wrote:

We see this error 75% of the time. Have you guys made an progress on
resolving the issue ?

On Sep 6, 8:14 pm, archF6 <tylerjpeter...@gmail.com> wrote:
> 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 <rudi.far...@gmail.com> wrote:
>
>
>
> > I have seen this same http page with empty body
> > <!DOCTYPEhtmlPUBLIC "-//W3C//DTDHTML4.01//EN" "http://www.w3.org/
> > TR/1999/REC-html401-19991224/strict.dtd">
> > <!-- <!DOCTYPEHTMLPUBLIC "-//W3C//DTDHTML4.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.jsonfrom209.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 statushtmlresponse from the json > > > > > search api which look like this, most times the same search works
> > > > > fine, it just happens occassionally:
>
> > > > > <!DOCTYPEhtmlPUBLIC "-//W3C//DTDHTML4.01//EN" "http://www.w3.org/
> > > > > TR/1999/REC-html401-19991224/strict.dtd">
> > > > > <!-- <!DOCTYPEHTMLPUBLIC "-//W3C//DTDHTML4.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?- Hide quoted text -
>
> - Show quoted text -

Reply via email to