Hi all,
Some changes were just deployed and it looks like there may be a
bug. I'm looking into it now … hold tight and I'll update you all when
I know more.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Jul 9, 2009, at 4:25 PM, dean.j.robinson wrote:
Everyone just
Yes, my application - which was working this morning - is now getting
401s on every OAuth request.
Something changed.
On Jul 9, 7:25 pm, dean.j.robinson dean.j.robin...@gmail.com
wrote:
Everyone just magically got logged out of my hahlo4 beta, which was
working fine an hour ago, and now when
Subject: [twitter-dev] Re: Has something with OAuth changed?
Yes, my application - which was working this morning - is now getting
401s on every OAuth request.
Something changed.
On Jul 9, 7:25 pm, dean.j.robinson dean.j.robin...@gmail.com
wrote:
Everyone just magically got logged out of my hahlo4
Thanks for the super speedy response Matt.
On Jul 10, 9:26 am, Matt Sanford m...@twitter.com wrote:
Hi all,
Some changes were just deployed and it looks like there may be a
bug. I'm looking into it now … hold tight and I'll update you all when
I know more.
Thanks;
– Matt
Awesome, thanks Matt, seems to be all working normally here too.
On Jul 10, 10:37 am, Matt Sanford m...@twitter.com wrote:
Hi all,
The issue has been fixed and from my testing it looks like things
are back to normal.
Sorry for the disruption;
– Matt Sanford / @mzsanford
Still not working here.
http://twitter.com/oauth/request_token?oauth_consumer_key=***oauth_nonce=8995570oauth_signature_method=HMAC-SHA1oauth_timestamp=1247187445oauth_version=1.0oauth_signature=s9fxOOJhdVjLr3pacFF0uvBXxFE%3d;
...gets 401 Unauthorized.
On Jul 9, 8:53 pm,
Hi,
Same here, we re getting 401 on every OAuth requests.
thanks,
johann
@romefort
CTO @ Seesmic
On Jul 9, 4:29 pm, Duane Roelands duane.roela...@gmail.com wrote:
Yes, my application - which was working this morning - is now getting
401s on every OAuth request.
Something changed.
On
On my side, things are back to normal since Matt announcement.
On the previous bug, the error message attached in the body was Could
not authenticate you. Are you receiving the same error message?
Arnaud.
On Jul 10, 1:34 am, johann romef...@gmail.com wrote:
Hi,
Same here, we re getting 401
I'm getting the same thing I was getting earlier: 401 Unauthorized
On Jul 9, 10:16 pm, Arnaud Meunier arnaud.meun...@twitoaster.com
wrote:
On my side, things are back to normal since Matt announcement.
On the previous bug, the error message attached in the body was Could
not authenticate
Unauthorized probably referes to the official description of the
HTTP 401 Code. I was wondering what was the Twitter error message you
received (if any) in the body of your response. Could be something
like Invalid / used nonce or Invalid / expired token...
Arnaud.
On Jul 10, 4:18 am, Duane
10 matches
Mail list logo