witter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com
] On Behalf Of Roy Hooper
Sent: Thursday, September 10, 2009 9:04 AM
To: Twitter Development Talk
Subject: [twitter-dev] Re: Random 408 errors having been appearing
the last 48 hours
I'm still seeing
...@googlegroups.com] On Behalf Of Roy Hooper
> > Sent: Thursday, September 10, 2009 9:04 AM
> > To: Twitter Development Talk
> > Subject: [twitter-dev] Re: Random 408 errors having been appearing the last
> > 48 hours
>
> > I'm still seeing this recurring prob
velopment-t...@googlegroups.com] On Behalf Of Roy Hooper
> Sent: Thursday, September 10, 2009 9:04 AM
> To: Twitter Development Talk
> Subject: [twitter-dev] Re: Random 408 errors having been appearing the last
> 48 hours
>
> I'm still seeing this recurring problem. Are only oaut
-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of Roy Hooper
Sent: Thursday, September 10, 2009 9:04 AM
To: Twitter Development Talk
Subject: [twitter-dev] Re: Random 408 errors having been appearing the
I'm still seeing this recurring problem. Are only oauth users
experiencing this? If so, maybe its time for us to give up on OAuth?
On Sep 9, 12:16 pm, John Kalucki wrote:
> Point your mobile device through a web proxy that you control. Monitor
> the traffic there with tcpdump.
>
> On Sep 9, 7:
Thank John,
I wish it were that simple, it does not happen as often when the
request doesn't come from the Mobile Carriers servers.. Our client
actually makes use of direct to twitter connections (thorugh mobile
carrier) as well as proxied connections through our servers depending
on the a
Point your mobile device through a web proxy that you control. Monitor
the traffic there with tcpdump.
On Sep 9, 7:07 am, Naveen A wrote:
> It might be useful if detailed (step by step) instructions of how to
> generate the debug information twitter needs to track down this HTTP
> data being re
It might be useful if detailed (step by step) instructions of how to
generate the debug information twitter needs to track down this HTTP
data being returned on the API, I am not sure how much data you are
getting but I would really like to provide as much as I possibly can
and provide others with
For our app, this started happening just after the DOS attacks and
have persisted since then. So my suspicion is that the 408 error is a
throttling mechanism. 408 is a connection read timeout. The problem as
I see it is that there is no way that the exception could get thrown
so fast if there were
If you are having connection problems like this, please send your IP
address, account(s), a curl(1) -vvv trace, and a tcpdump of the
failure to a...@twitter.com.
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter inc.
On Sep 7, 5:02 pm, fablau wrote:
> I am having the same issue, most
I am having the same issue, most of the times I cannot connect to
Twitter, I get 408 error and the API is mostly unusable form my side.
I am able to connect just a couple of times every 36-48 hours! Are we
the only people having this issue? How that can be possible? Is there
any way to contact Twi
We've been seeing 408's since the DOS attack back in July/August.
They feel like rate limiting on Twitter's part when overloaded.
Cannot tell since 408 isn't listed as an error they throw at
api.twitter.com
JEff
On Sep 6, 8:51 am, bosher wrote:
> Random 408 errors are being returned when user
12 matches
Mail list logo
