[twitter-dev] Re: Twitter API returning truncated XML responses

2009-04-15 Thread Doug Williams
Dossy, More details would certainly help track down the problem. Headers, response bodies, etc.? Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 15, 2009 at 12:57 PM, Dossy Shiobara do...@panoptic.com wrote: Hi, Is there something actively killing the Twitter web

[twitter-dev] Re: Twitter API returning truncated XML responses

2009-04-15 Thread Chris Thomson
I'm having this issue as well. Here's the full response (including the headers returned): http://dl.getdropbox.com/u/14675/twittercom_statuses_followers.xml.txt -Chris Thomson http://twitter.com/chris24 On Wed, Apr 15, 2009 at 4:44 PM, Doug Williams d...@twitter.com wrote: Dossy, More details

[twitter-dev] Re: Twitter API returning truncated XML responses

2009-04-15 Thread Dossy Shiobara
On 4/15/09 4:44 PM, Doug Williams wrote: More details would certainly help track down the problem. Headers, response bodies, etc.? Here's a network trace: GET /statuses/followers.xml?page=2 HTTP/1.0 Accept: */* Host: twitter.com User-Agent: Tcl http client package 2.5.5 Authorization: Basic

[twitter-dev] Re: Twitter API returning truncated XML responses

2009-04-15 Thread Dossy Shiobara
On 4/15/09 5:08 PM, Chris Thomson wrote: I'm having this issue as well. Here's the full response (including the headers returned): http://dl.getdropbox.com/u/14675/twittercom_statuses_followers.xml.txt Phew! I thought I was the only one ... -- Dossy Shiobara |

[twitter-dev] Re: Twitter API returning truncated XML responses

2009-04-15 Thread Doug Williams
Thanks for the report Dossy, et. al. I see your problem now with the supplied output. I'll the operations folks know about this. Not an API issue but something higher up the chain. Stay tuned... Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 15, 2009 at 2:19 PM, Dossy

[twitter-dev] Re: Twitter API returning truncated XML responses

2009-04-15 Thread Dossy Shiobara
On 4/15/09 5:46 PM, Doug Williams wrote: Thanks for the report Dossy, et. al. I see your problem now with the supplied output. I'll the operations folks know about this. Not an API issue but something higher up the chain. Stay tuned... Thanks! If your Ops folks need any data, feel free to