They went away for a bit... and now not only am I getting 408's on
update but validate credentials is failing as well....

On Aug 6, 2:56 pm, briantroy <brian.cosin...@gmail.com> wrote:
> Now twitter search API calls are hanging... just stall until they time
> out on my side....
>
> On Aug 6, 2:30 pm, Matthew F <mcf1...@gmail.com> wrote:
>
>
>
> > I'm getting 408s trying to authenticate with OAuth
>
> > On Aug 6, 10:20 pm, John Kalucki <jkalu...@gmail.com> wrote:
>
> > > This should be fixed for the Streaming API.
>
> > > -John
>
> > > On Aug 6, 1:59 pm, Jennie Lees <trin...@gmail.com> wrote:
>
> > > > Getting the same thing using the track function of the API.
>
> > > > On Thu, Aug 6, 2009 at 9:43 PM, briantroy <brian.cosin...@gmail.com> 
> > > > wrote:
>
> > > > > Sorry... these are HTTP 408s...
>
> > > > > On Aug 6, 1:20 pm, briantroy <brian.cosin...@gmail.com> wrote:
> > > > > > This just started today. It was working fine before and early this
> > > > > > morning.
>
> > > > > > I'm send in user updates from a widget via API. My server is
> > > > > > whitelisted and I've got a registered "service". I get a HTTP 409 on
> > > > > > every attempt to submit a status.
>
> > > > > > Not sure why... You can try it here:http://briantroy.com/blog/about
>
> > > > > > I know a 409 should mean timed out... but the response comes back in
> > > > > > one second (or just really really fast).
>
> > > > > > Any help appreciated...
>
> > > > > > Brian Roy
>
> > > > > > justSignal
>
> > > > --
> > > > Jennie Lees
> > > > Founder, Affect Labs
> > > > jen...@affectlabs.comhttp://twitter.com/jennielees

Reply via email to