I have confirmed a problem with xAuth/OAUth that I believe resides
within Twitter OAuth implementation that has been a thorn in our side
for a while. I say *believe* because I do not claim to know for sure,
thus this post.
I assume no one at Twitter will be inclined to do me any favours, but
Sent: Tuesday, May 25, 2010 7:40 PM
To: Twitter Development Talk
Subject: [twitter-dev] Twitter OAuth Timestamps
I have confirmed a problem with xAuth/OAUth that I believe resides within
Twitter OAuth implementation that has been a thorn in our side for a
while. I say
*believe* because I
@googlegroups.com [mailto:twitter-
development-t...@googlegroups.com] On Behalf Of Eric Woodward
Sent: Tuesday, May 25, 2010 7:40 PM
To: Twitter Development Talk
Subject: [twitter-dev] Twitter OAuth Timestamps
I have confirmed a problem with xAuth/OAUth that I believe resides within
Twitter
On Tue, 25 May 2010 19:49:28 -0500
Brian Smith br...@briansmith.org wrote:
This is known and expected behavior. There have been other threads
about it in the last couple of weeks. If you get a 401 response, you
should compare the Date header of Twitter's response to the current
system time.
