Most 401 Unauthorized errors (and especially the ones involving UTF8
characters) are because of errors in the Base String, used to generate
the signature.

Please use the validation tool at <http://quonos.nl/oauthTester>, it may
help you a lot with validating your Base String. As access_token always
involves usernames and passwords, please do substitute them with dummy
ones for security reasons - just make sure that they at least look like
the previous ones, because otherwise it would be hard to detect encoding


PS: When dealing with encoding issues, XXXXXX'ing the values really
doesn't help.

On 11/1/10 6:58 PM, pawan wrote:
> Hi,
> We have created a Desktop Twitter application, In this application I
> have used XAuth feature to get data from "Twitter API". It works fine
> on Win 7 Ultimate machine. However when I run my application's exe on
> core "Chinese" Win 7 machine, I got "The remote server returned an
> error: (401) Unauthorized." error from following request:
> https://api.twitter.com/oauth/access_token?oauth_consumer_key=XXXXXXXXXXXX&oauth_nonce=9644877&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1288573328&oauth_version=1.0&x_auth_mode=client_auth&x_auth_password=XXXXXX&x_auth_username=XXXXXXXX&oauth_signature=XXXXXXXXXXX
> Can anyone help me out to know how to resolve this issue.
> Thanks,
> Pawan

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: 

Reply via email to