As far as we know this is resolved and things should be working fine.
I'm not familiar with your setup so need to ask if you applied for xAuth and
were granted it?
If not that will be the causes of the 401. If you did what API call are you
trying to make and what does your signature base string lo
Guys- did this get resolved for you? Or are you still having issues?
I'm getting a 401 error with xauth.
On Jul 19, 6:10 pm, Isaiah Carew wrote:
> OK, good to know. Just want to make sure it's not just me. Misery loves
> company, I guess. :-P
>
> isaiahhttp://twitter.com/isaiah
>
> On Jul 19,
OK, good to know. Just want to make sure it's not just me. Misery loves
company, I guess. :-P
isaiah
http://twitter.com/isaiah
On Jul 19, 2010, at 2:54 PM, Tim Davies wrote:
> Im getting the same isalah. Twitter are aware of the issue. its during
> handshake for creating new tokens and maybe
Im getting the same isalah. Twitter are aware of the issue. its during
handshake for creating new tokens and maybe linked to several other
OAuth issues that came to attention this morning.
Im hoping it will be fixed shortly!
Isaiah,
I seem to be getting similar errors with regular OAuth requests. If
I'm already logged into twitter and OAuth just needs to redirect, it
works, but if I land on the login page, enter my username and password
and click submit, the redirect breaks with the 500 error.
Ashish
On Jul 19, 3:10
