For the last few days, *every* single OAuth request I issue has been met
with a 401.
Also, trying to access this URL, the OAuth app details page for Twitter
Karma, results in a fail whale - consistently:
http://twitter.com/oauth_clients/details/1574
Is OAuth down for everyone, or just me?
--
Hi Dossy,
While we have been having some performance issues that should give you
occasional 401s, it shouldn't be as widespread as the experience you've been
having.
When we throw a 401, we typically provide an error message within the body
of the response -- if you can share that it would be
On 5/20/10 3:16 PM, Taylor Singletary wrote:
While we have been having some performance issues that should give you
occasional 401s, it shouldn't be as widespread as the experience you've
been having.
OK, you know, until *literally* 60 seconds ago, requests for
Sorry you're having trouble, Dossy.
Can you share the complete path you're using to fetch a request token (with
host, domain, protocol, path, and any query parameters), your signature base
string, and an authorization header if you're using header-based auth?
Taylor Singletary
Developer
Hey guys,
Don't know if this is related, but I was testing a friend's iPad app
this morning which uses xAuth.
When setting up a new account in his app, the app authorizes in my
Connections tab. However, whenever his app tries to use the tokens,
we get an immediate HTTP 401. None of the calls
i support dossy too
From: Taylor Singletary taylorsinglet...@twitter.com
To: twitter-development-talk@googlegroups.com
Sent: Thu, May 20, 2010 1:27:26 PM
Subject: Re: [twitter-dev] Is OAuth working for *anyone* out there?
Sorry you're having trouble, Dossy
Just tried establishing a new connection to a different account with
Twitterrific (which I believe uses xAuth) and it worked fine.
So, there is presumably a bug in the iPad client I was testing. Unrelated.
-damon
On Thu, May 20, 2010 at 3:33 PM, Damon Clinkscales sca...@pobox.com wrote:
Hey
Hi Damon,
We've heard some reports of iPads setting their dates/clocks incorrectly --
sometimes back to 1969. If the client application uses the date/time on the
machine (rather than querying it from some other source), and the date/time
isn't within 5 minutes or so of our clocks, it results in a
On Thu, May 20, 2010 at 4:16 PM, Taylor Singletary
taylorsinglet...@twitter.com wrote:
Hi Damon,
We've heard some reports of iPads setting their dates/clocks incorrectly --
sometimes back to 1969. If the client application uses the date/time on the
machine (rather than querying it from some
Dossy, to echo my comment to Damon -- can you check the timestamps on your
server that is issuing requests? If every call of yours is failing, it's
possible that that is why.
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Thu, May 20, 2010 at 12:29 PM, Dossy Shiobara
I'll send it to you privately, off-list.
On 5/20/10 4:27 PM, Taylor Singletary wrote:
Sorry you're having trouble, Dossy.
Can you share the complete path you're using to fetch a request token
(with host, domain, protocol, path, and any query parameters), your
signature base string, and an
AHA! I just checked, somehow my system clock is off (slow) by ~3 hours.
Somehow, NTP died and time sync stopped.
I'm not sure how that happened, but I restarted ntpd everywhere, and
OAuth is working again!
Would it be a huge deal to ask that if the OAuth request is being
refused due to the
12 matches
Mail list logo
