The 502s don't really bother me. It just slows me down a bit. My
Twitter lib automatically retries a request that 502'd.

The 200 OK responses that come back with the X-RateLimit headers
missing happen on all kinds of requests, both GETs and POSTs (more on
GETs as far as I can tell), and as far as I can see there is no
pattern. One request would return headers, and the very next request
to the same API method would not return the headers. Are these perhaps
requests have have been 302'd? I can't really check because cURL is
following the redirects on GETs.


On Aug 10, 12:19 pm, Ryan Sarver <rsar...@twitter.com> wrote:
> Can you all provide full packet dumps of the issues you are seeing? That
> will help us debug the type of request you are making and what the full
> response looks like.
> Thanks, Ryan
> On Mon, Aug 10, 2009 at 8:15 AM, Duane Roelands 
> <duane.roela...@gmail.com>wrote:
> > My users are seeing these as well.
> > On Aug 10, 10:22 am, Dewald Pretorius <dpr...@gmail.com> wrote:
> > > Just to let you guys know that 502 Bad Gateway responses are coming
> > > thick and fast this morning (Monday).
> > > Dewald

Reply via email to