Re: [twitter-dev] Re: Seeing weird, malformed HTTP responses? We're on it.
We continue to work on the issues and will be posting updates to
http://status.twitter.com as we have news. Please check there for the most
up to date details.
Thanks for your patience and support as we work through these issues.
Best,
Matt
On Mon, Jul 19, 2010 at 10:08 PM, Jason LaFollette
jason.lafolle...@gmail.com wrote:
Incase it helps anyone investigating...
users/lookup.json returns a complete response when I access it through
a web browser or fiddler.net
users/lookup.json returns a partial response when I access it
programmatically through a .NET WebRequest or through curl from an OSX
command line
I originally thought it might be http request headers, but I've
stripped out ever header except Auth within fiddler and I continue to
get full responses.
On Jul 20, 12:59 am, goodtest goodtest...@gmail.com wrote:
+1
On Jul 19, 9:25 pm, Cameron Kaiser spec...@floodgap.com wrote:
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.
Ditto for direct_messages.json, although the main timeline is a bit
better.
--
personal:
http://www.cameronkaiser.com/--
Cameron Kaiser * Floodgap Systems *www.floodgap.com*
ckai...@floodgap.com
-- When you don't know what you're doing, do it neatly.
---
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
[twitter-dev] Re: Seeing weird, malformed HTTP responses? We're on it.
Except that I find status.twitter.com is the last place to look for any information about faults. We're getting the flak from users for around 3-4 hours before anything relating to the issue appears on status, and the only official tweets come from the twitterapi account which none of the users follow. Ryan On 20 July, 07:22, Matt Harris thematthar...@twitter.com wrote: We continue to work on the issues and will be posting updates tohttp://status.twitter.comas we have news. Please check there for the most up to date details. Thanks for your patience and support as we work through these issues. Best, Matt On Mon, Jul 19, 2010 at 10:08 PM, Jason LaFollette jason.lafolle...@gmail.com wrote: Incase it helps anyone investigating... users/lookup.json returns a complete response when I access it through a web browser or fiddler.net users/lookup.json returns a partial response when I access it programmatically through a .NET WebRequest or through curl from an OSX command line I originally thought it might be http request headers, but I've stripped out ever header except Auth within fiddler and I continue to get full responses. On Jul 20, 12:59 am, goodtest goodtest...@gmail.com wrote: +1 On Jul 19, 9:25 pm, Cameron Kaiser spec...@floodgap.com wrote: 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. Ditto for direct_messages.json, although the main timeline is a bit better. -- personal: http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- When you don't know what you're doing, do it neatly. --- -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Re: Seeing weird, malformed HTTP responses? We're on it.
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
[twitter-dev] Re: Seeing weird, malformed HTTP responses? We're on it.
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
Re: [twitter-dev] Re: Seeing weird, malformed HTTP responses? We're on it.
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. Ditto for direct_messages.json, although the main timeline is a bit better. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- When you don't know what you're doing, do it neatly. ---
[twitter-dev] Re: Seeing weird, malformed HTTP responses? We're on it.
+1 On Jul 19, 9:25 pm, Cameron Kaiser spec...@floodgap.com wrote: 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. Ditto for direct_messages.json, although the main timeline is a bit better. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- When you don't know what you're doing, do it neatly. ---
[twitter-dev] Re: Seeing weird, malformed HTTP responses? We're on it.
Hi, Thanks for the announce, I just wish I'd noticed it 4 hours ago ;( 'Tis indeed bizarre, and sends cURL loopy :) Good luck! - Paul
[twitter-dev] Re: Seeing weird, malformed HTTP responses? We're on it.
look forward to the fix soon Taylor! -Raj On Jul 19, 1: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
[twitter-dev] Re: Seeing weird, malformed HTTP responses? We're on it.
Incase it helps anyone investigating... users/lookup.json returns a complete response when I access it through a web browser or fiddler.net users/lookup.json returns a partial response when I access it programmatically through a .NET WebRequest or through curl from an OSX command line I originally thought it might be http request headers, but I've stripped out ever header except Auth within fiddler and I continue to get full responses. On Jul 20, 12:59 am, goodtest goodtest...@gmail.com wrote: +1 On Jul 19, 9:25 pm, Cameron Kaiser spec...@floodgap.com wrote: 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. Ditto for direct_messages.json, although the main timeline is a bit better. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com*ckai...@floodgap.com -- When you don't know what you're doing, do it neatly. ---
