OK. One other thing I've just noticed looking over your Authorization header is that your oauth_verifer and oauth_token are set to the same value. This is unusual and not something I would expect. Double check your code used the oauth_verifier we return to you in the callback URL and the token is the one you received in the request_token request.
Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Fri, Dec 17, 2010 at 2:40 PM, Brian Gunn <gun...@gmail.com> wrote: > I was hoping that URL is the basestring. Apparently not. > > What do you mean by basestring? I'm using the Tweepy Python library > to hide the details of this from me, but I'm digging through there to > instrument it so I can send you what you want. > > Brian > > On Dec 17, 2:37 pm, Matt Harris <thematthar...@twitter.com> wrote: > > Hi Brian, > > > > A couple of questions so we can investigate: > > > > 1. What was the response body content we returned with the 401? > > 2. What was the basestring you used? > > > > Best > > @themattharris > > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > > > > > > > > > > > > > > On Fri, Dec 17, 2010 at 2:30 PM, Brian Gunn <gun...@gmail.com> wrote: > > > Hi all. > > > > > I am working on a web app for Twitter using the Tweepy Python API. My > > > code has been working for a month, but at some point this week, it > > > stopped working. Now when I request the access token from the > > > verification code, I get a 401: Unauthorized failure. > > > > > I did see from Matt's post yesterday that Tweepy was using the wrong > > > URLs. (It was usinghttp://twitter.com/oauthinstead of > > >http://api.twitter.com/oauth.) I fixed that problem and I'm still > > > seeing the problem. > > > > > I see from everyone else who is reporting this that you want to see > > > the basestring and Authorization header, so here's what I'm using: > > > > > URL:http://api.twitter.com/oauth/access_token > > > Headers: {'Authorization': 'OAuth realm="", oauth_nonce="58011146", > > > oauth_timestamp="1292624570", oauth_signature_method="HMAC-SHA1", > > > oauth_consumer_key="bSf2ywUggWN1w7Yx5FtvJg", > > > oauth_verifier="8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0", > > > oauth_version="1.0", > > > oauth_token="8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0", > > > oauth_signature="tOqtyU6E%2FulE8xiYBQRzuv2RMog%3D"'} > > > > > Does anyone see a problem here? > > > > > Thank you! > > > > > Brian > > > > > -- > > > Twitter developer documentation and resources: > http://dev.twitter.com/doc > > > API updates via Twitter:http://twitter.com/twitterapi > > > Issues/Enhancements Tracker: > > >http://code.google.com/p/twitter-api/issues/list > > > Change your membership to this group: > > >http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
