On 8/17/10 5:35 AM, Colin Hill wrote:
I ran into an issue when authenticating via OAuth, using the
token/secret pair offered for one of my apps, on the dev site (example)
http://dev.twitter.com/apps/12345/my_token
we use the perl OAuth::Lite::Consumer module and have no difficulty
Hi Colin,
Right now we report nonce errors in a few cases -- not all of them having
much to do with nonces unfortunately.
Check that the clock on the machines you are executing this on are within 5
minutes of the clock on api.twitter.com -- one easy way to do this before
you even start making
Tom,
That was my first thought as well, but in that case, I would expect
the request failures to be randomly distributed and relatively
infrequent. In this case it fails every time (tested over a period of 6
hours yesterday). I've also not encountered this issue with any of the
other OAuth
That was my first thought as well, but in that case, I would expect
the request failures to be randomly distributed and relatively
infrequent. In this case it fails every time (tested over a period of 6
hours yesterday). I've also not encountered this issue with any of the
other OAuth
I'll quote some more :
To avoid the need to retain an infinite number of nonce values for
future checks, servers MAY choose to restrict the time period after
which a request with an old timestamp is rejected. Note that this
restriction implies a level of synchronization between the
Taylor,
Good catch. Thanks. It was in fact a timestamp issue. The virtual
server I was using to test our twitter code hadn't been fired up in a
few weeks so before conducting yesterday's work, I updated the system
packages which included the kernel, but failed to rebuild the guest
tools which
