Any update on these messed up responses? I'm currently seeing users/
lookup.json responses get truncated if I request more than a small
number of users.

Hayes

On Jul 19, 4:28 pm, jsleuth <jsle...@gmail.com> wrote:
> Yes indeed.  It's a weird one.
>
> Thanks for the feedback.
>
> JS
>
> On Jul 19, 4:36 pm, Taylor Singletary <taylorsinglet...@twitter.com>
> wrote:
>
>
>
> > Hi Developers,
>
> > Along with a host of other issues we've been keeping you in the loop 
> > onhttp://status.twitter.com--we have another issue that a number of you have
> > pointed out:
>
> > *Our HTTP responses appear to be insane.*
>
> > - We're sending Content-Length twice, with differing numbers -- and
> > generally sending duplicate HTTP headers as a whole.
>
> > - We're sending the incorrect Content-Type corresponding to the response
> > format you are requesting (though the content itself is likely in the format
> > you are expecting).
>
> > - We're truncating response bodies.
>
> > We've got the team looking into this right now. It's too early for an ETA on
> > a fix.
>
> > Thank you for your patience. This is, admittedly, a pretty weird issue.
>
> > Taylor

Reply via email to