Intermittent OAuth issue

Doriemae07 · 2012-01-13T16:26:47.000Z

@episod, What are you doing in my account, in my e-mail, and messing around with all my old e-mail addresses. Why can’t you people leave me alone or tell me what you want to know?

episod · 2012-01-13T16:43:19.000Z

Have you mistakenly subscribed to notifications from this site dev.twitter.com? It sends emails to the email address associated with your Twitter account. To turn off email notifications, go to https://dev.twitter.com/user

skakri · 2012-01-13T16:59:42.000Z

Yeah, the problem was on our side, sorry.

4EE_Group · 2012-01-16T00:16:50.000Z

We are seeing intermittent 401 errors with one client. A repeatable fix is for the client to go into his twitter account, uncheck Tweet Location, Save. Then go back and check Tweet location and Save. At that point, the 401 errors disappear until the next occurrence.

Any thoughts?

vuhoanghieu · 2012-01-16T03:27:13.000Z

ctrl +shift+delete

4EE_Group · 2012-01-16T20:02:21.000Z

My client says that during a resend, the message clears. He may send 10 more tweets and then see another 401 error.

This appears to be account dependent. I’m not seeing this with other clients.

He also had trouble receiving account credentials during an Oauth sign-in. He made a modification to his profile, saved the change, went back to the app and had a successful sign-in session, receiving his credentials.

One solution is to ignore the first 401 response and try again. But, that does not solve the account sign-in problem for this client.

His clock is automatically updated. The xml error response from Twitter is: “Could not authenticate with OAuth.”

The app is only posting messages via status updates.

sneiland · 2012-01-17T16:27:36.000Z

I am also seeing this error crop up today. Neither my app code or credentials have changed but getting 401 responses.

antonclicker · 2012-01-17T21:49:08.000Z

it looks like, Twitter may be sending a wrong HTTP code in this case. Probably should be a 500 (server error) or a 400 (invalid request), but not a 401.

if i POST to https://stream.twitter.com/1/statuses/filter.json with data “track=#lost”, it works fine. But if the tag contains a star, like this: “track=#*lost”, then i get the 401 error.

Interestingly enough, the exact same query (with the star) works without a problem if Basic Authentication is used instead of OAuth.

episod · 2012-01-17T22:10:46.000Z

It all depends on where in the stack the evaluation errors. Both “#” and “*” are reserved characters when you’re using them without special meaning – in the context of a hashtag, the “#” character MUST be provided to either the querystring or the POST body as %23 and the OAuth signature basestring must represent it as %2523.

What often happens is that the HTTP library still sends the character as a literal, and the OAuth basestring double encodes it. Or the HTTP library correctly escapes it but the OAuth basestring doesn’t it encode the value again. Or any combination of these comedy of errors.

Ultimately, for a signature to be validated both the mechanics of HTTP and parameter passing need to be correct and in agreement. Reserved characters need to be encoded correctly in the query & POST body before being sent to the OAuth signature algorithms.

Lots of HTTP libraries out there try doing the right thing when given character literals that should be encoded, but the accompanying OAuth library doesn’t know about the “right thing” the HTTP library is doing.

4EE_Group · 2012-01-18T00:20:05.000Z

Our client had a repeatable problem with the signIN process. He could not receive credentials. He went to his twitter account on the web, made a change to his profile, saved, changed back, save and then was able to signON with the app… confirmed credentials.

Today, our app was working fine for him. He approved another app and then started getting 401 errors again. They later cleared.

No apparent rhyme or reason…

episod · 2012-01-18T16:05:48.000Z

Make sure that the client is using HTTPS for all the OAuth operations (and likewise the API) – there are some developers who have reported unwittingly passing cookies around to methods like oauth/request_token that require the connection to be completed over SSL – this is especially likely in an environment like browser plugins, Flash, and so on.

gnanavel_raja · 2012-01-20T06:37:11.000Z

when i try to get data from my twitter account using twitter api .
i use command for get follwers they show error like unauthorised user cannot access personal data.
thanks.

educompsci · 2012-03-08T13:56:58.000Z

Until yesterday it was working fine, but today the userstream is returning me status 401. I think it is related with this issue here.

The response header is:

Content-Type: text/html
WWW-Authenticate: Basic realm="Firehose"
Cache-Control: must-revalidate,no-cache,no-store
Content-Length: 1505
Connection: close

educompsci · 2012-03-08T14:12:43.000Z

Finally! sudo ntpdate ntp.ubuntu.com made it work again! Do it to sync your clock!

asmitasingh15 · 2012-05-14T04:50:31.000Z

I am getting continous ‘HTTP/1.1 401 Unauthorized’ as response after log in twitter account.
My clocks are synced. Can’t understand the problem.

comuniquese · 2012-05-23T19:14:31.000Z

hello I’m getting error 401 when tweeting words with accent. For example, “alguém está ai” If I tweet “alguem esta ai” no accent, everything happens perfectly.

Can anyone help me?

My language is portuguese.

educompsci · 2012-05-23T20:43:06.000Z

My language is Portuguese also, I’ve created a Python applet for an open source application to communicate with Twitter. It works flawlessly, even when I type accents, and special characters. What language are you using?

comuniquese · 2012-05-23T21:01:14.000Z

I am using c #. Net, now tried changing the Encode ASCII to UTF8 and it worked, but my tweet is with “?” where is the accents.

MySmileInspires · 2012-06-28T14:56:32.000Z

I’m having a similar problem. I’m a user of UberSocial and whenever I try to check my Timeline on interactions a message pops up and says " Error validating twitter credentials could not authenticate OAuth ". I’m 15 and totally oblivious as to what is going on. I re-installed it 3 times, revoked access to the app and the problem is still occurring.

lupislune · 2012-06-28T16:37:44.000Z

I’m having the same problem on two different computers on two different networks. Twhirl and Tweetdeck which work fine on both networks, suddenly stopped working yesterday. When looking at the log files, I get Oauth errors. Both systems are Windows 7, 64 bit.