Hi Taylor,
Thank you for your response.
Originally, I did forget to add an oauth_timestamp field. I've since included
one, but still have the same problem. I modified my app to dump out the base
string. Here's what I got:
An interesting note, perhaps. I was writing unit tests last night to check my
OAuth implementation. I was able to connect and retrieve data via the regular
API (api.twitter.com), but I still have the 401 issue when trying to connect to
the user stream API.
On 2011-06-24, at 19:54, Eryn Wells
Hello all,
I'm quite new to OAuth and the Twitter API, and this is my first post to this
list.
I'm working on an app in Python using the Twisted framework. It uses brosner's
fork of python-oauth2[1] to do the initial authentication and subsequent
request signing. I'm using the PIN code flow
Hello,
I am a Java developer working on a web application that makes use of
the Twitter API. We use the Signpost library (version 1.2.1.1) to
perform OAuth and issue API requests, and have been doing so
successfully for months. We have been signing our requests with a
whitelisted key and secret
Hi Christopher,
Could you attempt to get the response body for the request either by
repeating the request or enhancing your logs. The reason for the 401 is
communicated in the response body and knowing that will help explain what is
going on.
Best,
@themattharris
Developer Advocate, Twitter
Hi
On blackberry with httpConnection, I need to add network transport
string such as ;interface=wifi to the url.
The problem is, once I added the network transport string, I get 401
unauthorized for status update and GET statuses/user_timeline.
If I remove the transport string, then I can POST
There is an active thread for this issue
http://code.google.com/p/twitter-api/issues/detail?id=2118 you're not alone
on this one, there are many people suffering from this issue.
On Tue, Mar 29, 2011 at 6:26 AM, naresh naresh.d...@gmail.com wrote:
Hi
We have integrated our web application to
Is anyone else experiencing any 401 errors all of a sudden? I was doing
some testing this morning and was logging in fine using twitter and then 10
min later I started getting 401 unauthorized errors.
Thanks,
Trevor
--
Twitter developer documentation and resources:
Hi Trevor,
Could you share the request and response you are sending so we can
investigate. Remember to obscure user and consumer secrets.
Thanks,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Sat, Mar 19, 2011 at 5:47 AM, Trevor Dean trevord...@gmail.com wrote:
We're getting a ton of 401 errors when people are trying to OAuth
against some of our sites. These sites have been in production for
years (and one new one went up yesterday). When we get the error, we
get no message in the Response. From the client perspective, it
happens when you click the
Ryan's just told me they're currently aware of the issue and looking into it.
On 18 Mar 2011, at 19:13, Ninjamonk wrote:
I am also getting these problems. They have been on and off all day.
The same code works fine and 5 mins later it throws 401's and its been
working for 6 months no
I have an application that contains a simple setup using the
oauthtwitter library found here.
http://code.google.com/p/oauth-python-twitter/
#Example code
twitter = app.extras.oauthtwitter.OAuthApi(CONSUMER_KEY,
CONSUMER_SECRET)
request_token = twitter.getRequestToken()
oauth_verifier =
Hi John,
What is the does the body of the error response say? The message will tell you
which part of the oauth request failed.
Also be aware that oauth timestamps are in UTC seconds.
Best,
@themattharris
On Feb 4, 2011, at 12:45, john john.g...@gmail.com wrote:
I have an application that
Hi Taylor,
In order to test your 1st suggestion do you know if your HTTP
transport method munges any HTTP headers or adds its own HTTP headers
in any way? we created a simple test procedure on our public web
server, to simulate the google end point
https://api.twitter.com/oauth/access_token.
So
Hi Taylor,
In releatio to the 2nd test, I have used the values from
http://dev.twitter.com/pages/xauth and inserted these into my program
to step through the process.
Base string:
POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
%2Faccess_tokenoauth_consumer_key%3DJvyS7DO2qd6NNTsXJ4E7zA
Hi Taylor,
Success, the missing peice of the puzzle was that we needed to send
the post Body, which although it was explained in documentation, we
thought it was there for explanation of how the values are accumulated
for the base string.. seems obvious now, but when your trying to do
this for
Hi Taylor,
Now I have the Access Token and I use the explanations in
http://dev.twitter.com/pages/auth to make a request on users behalf, I
get a response from twitter:
Twitter Response= {errors:[{code:53,message:Basic
authentication is not supported}]}
Status= 401
StatusTxt= Unauthorized
I am
Hi Martin,
Thanks for your patience in working through xAuth with the issues you're
facing. Given the information you've provided, it's difficult to determine
exactly what might be amiss here.
I'm unfamiliar with the programming environment you are using -- do you know
if your HTTP transport
We had an application successfully talking to twitter for a few years
prior to oAuth, and now converting this application to xAuth and cant
get past the first step.
The application gets a 401 Unauthorized response when attempting to
get the access token.
Have confirmed our program when provided
I am getting an error executing the same code that has been working fine
until today. I am getting an error when attempting to get access token, the
error is Invalid / expired Token. I'm not sure what changed from
yesterday to today, any idea? I am running this code locally so the
callback is
Like the error says: your token is invalid or has expired. Make sure
that you are using the correct ones.
Tom
On 10/5/10 1:20 PM, Trevor Dean wrote:
I am getting an error executing the same code that has been working fine
until today. I am getting an error when attempting to get access
This code hasn't changed and was working yesterday and has been working for
many months. This error is happening right after the user has allowed the
application permission and is returning back to my application with tokens.
There is no chance for these tokens to expire so I don't think that
Please show your Base String. A lot of issues are related to the Base
String.
Also, to answer your question: yes, you need to combine both secrets.
consumersecretusersecret = your signing key.
Tom
On 9/12/10 12:09 AM, DK wrote:
I keep getting this when I try to update status. I am using xAuth
Hi~ I'm developing the twitter application with Android.
For posting twitpic data, I use Oauth echo, but I'v got 401 error.
Could not authentication you. (header rejected by twitter)
Oauth header
POST /2/upload.xml HTTP 1.1
x-auth-service-provider:
Did anything change in the API (couldn't find anything in the API changelog)
that would make all new users who are associating their Twitter acounts to
my app get a 401 on status update? All accounts up to a few days ago are
still working, newer ones get 401 using absolutely the same codebase and
Hi everyone,
I am developing an application using Twitter API and I have
encountered into a strange behavior connected with 401 error. I am
using basic auth. When I run my application locally, it works just
fine and I never get any 401 errors. However, when I run my
application on another
I am getting an error message when posting accent marks and other
diacritics in a status update.
I saw that there was an issue [1] posted in April of last year about
this problem. It seems to be with the signature generation for OAuth
with the encoding of accent marks.
I am using .Net(C#), and
Ooh, if this is the case then it will definitely stop me from using oAuth
for Feathers (http://feathersapp.com) since diacritics are an essential part
of Unicode art.
Very interested in hearing what you find out.
All the best,
Aral
On Tue, Feb 23, 2010 at 1:44 PM, eclipsed4utoo
I believe it has been fixed in some libraries in other programming
languages, but I can't figure out how to do it in .Net.
Ryan
On Tue, Feb 23, 2010 at 12:38 PM, Aral Balkan aralbal...@gmail.com wrote:
Ooh, if this is the case then it will definitely stop me from using oAuth
for Feathers
this would be news to me - if you have a way to replicate this, and you are
confident its not your oauth libraries, then please let me know.
On Tue, Feb 23, 2010 at 11:04 AM, Ryan Alford ryanalford...@gmail.comwrote:
I believe it has been fixed in some libraries in other programming
languages,
I think it is the way that .Net handles encoding of the diacritics. I don't
think it's a Twitter api issue. I was hoping that another .Net developer
had run into this issue and had fixed it.
Ryan
On Tue, Feb 23, 2010 at 2:07 PM, Raffi Krikorian ra...@twitter.com wrote:
this would be news to
My website uses twitter for authentication,
For the past 24 hours the OAuth sign in is continuously returning
401 , i am not able to figure out what to do?
Has some one faced similar problems?
My site has been down for 24 hours now because of this.
please help me out here.
I having this error for a while and is happening only on my machine, I
deploy the same project in another similar VM and it worked, so I am
starting to think that there might be something related to my
environment that is causing the 401 Unauthorized issue. I have a Mac
with OS 10.5.6 and a VM
I have been running into a recurring problem that I have been facing
for the past couple of days, on numerous machines.
I am extracting 200 tweets for a large number of users, using the
numeric user ID (user_id). After a small number of requests (between
10 and 50) I receive nothing but This
I am using python-auth, and oauth twitter to do backend authentication
via twitter sign in. It works as designed. I am able to get an
access_token and then use that to get the user info. I am having
trouble when it comes to trying to post a status update using the
oauth. I have pasted an example
I am getting 401 Unauthorized exception when updating status with
non english characters using my app.
This exception is happening for any Japanese or Korean characters.
Another interesting thing is that it is possible to post some other
non english characters like Malayalam. The exception will
Is Twitter still blocking posts to the API from non-white listed
apps? Since the DDOS attack we can't seem to send any posts through
the API using oAuth. Nothing in our code has changed but all was
working prior to the attack. Is anyone out there havine any success
sending messages with oauth
Are anyone experiencing 401 Unauthorized errors? Everything worked
fine before yesterday. Now we are getting 401 Unauthorized on both
basic authorization and OAuth on 80% of the calls. Other 20% works
fine.
What's happening?
I am using ASP .NET (VB) to try and authenticate using oAuth. I have
been able to get a request token and direct a user to Twitter's
authentication page. Twitter then redirects back to my app. At that
point I attempt to get an access token, but I continue to receive 401
unauthorized errors. I
I'm fairly sure I'm getting a proper token. Using the page
http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html I
get the same signature as in my failing url.
GET looks like:
http://twitter.com/friendship/exists.json?
oauth_consumer_key=Rg4VBVUvAoThpl78duF3Rg
My previous post is waiting to be moderated since I'm a newbie I
think, but I was wrong. I thought it was a get vs. post issue, but it
seems to be that my code works very intermittently. The error is
always a 401 unauthorized in getting the access token from the request
token. but once in a while
Hi everyone,
since about half an hour ago I seem to be getting 401 Unauthorized
responses to my OAuth-ed API calls.
Is that a known problem?
Regards,
Dominik
42 matches
Mail list logo
