We are getting this error, but Twitter is also sending back a valid

To clarify, if we post an update, the update appears in the timeline
but twitter returns a 401 error code (with the nonce message).

Same applies to friends timeline sometimes too.



On Apr 30, 12:46 am, Taylor Singletary <taylorsinglet...@twitter.com>
> We have a weird error condition in the OAuth implementation right now that
> throws invalid nonce errors when it's not necessarily the issue. We're still
> tracking what exactly causes this down, but believe that it's not applicable
> to the OAuth implementation rewrite we'll soon be rolling out.
> In the meantime, when you get this error and you're fairly certain you've
> never used the nonce before, if you can provide a signature base string and
> authorization header corresponding to the failed request it will give us
> better visibility into possible causation.
> Thanks!
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
> On Wed, Apr 28, 2010 at 7:15 PM, Dewald Pretorius <dpr...@gmail.com> wrote:
> > Cory,
> > I have had similar issues. When you get that 401 error, you need to
> > back off for a second or two, recalculate the nonce, and then resubmit
> > the request.
> > On Apr 28, 10:52 pm, Cory <cory.imdi...@gmail.com> wrote:
> > > Anyone have any ideas about this? I'm really not sure where to go or
> > > what to check from here, and I need to get this taken care of. Any
> > > information would be appreciated!

Reply via email to