Thanks for finding that, but twitter still refuses it
basestring:
POSThttp%3A%2F%2Fapi.twitter.com
%2Foauth%2Frequest%5Ftokenoauth_consumer_key%3DdHbWZ6idD9VEuQ5tNUufA%26oauth_nonce%3D6739551275477403%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1275477403%26oauth_version%3D1.0
Hi Arthur,
Unrelated: recommend using SSL for all the OAuth dance operations like
request_token, access_token, and authorize
Is there any chance you are providing the OAuth-related parameters as query
parameters in addition to providing them in the HTTP header? Have you
compared the timestamp
You are right, the encoded _ was the problem.
Thank you very much, now i can move to the other requests ^^
Arthur.
2010/6/2 Taylor Singletary taylorsinglet...@twitter.com
Hi Arthur,
Unrelated: recommend using SSL for all the OAuth dance operations like
request_token, access_token, and
Nevermind, sooner after posting this i found - Twitter requires that
all OAuth requests be signed using the HMAC-SHA1 algorithm
But i can't get it to work with hmac either :/
CONSUMERKEY = 'dHbWZ6idD9VEuQ5tNUufA';
CONSUMERSECRET = '5ZzUafGDoFcAqOEubv3TAa01xb0Z326NMK6fLLrmk0';
basestring:
i double checked the encryption of your base string against your
consumer key and your consumer secret and everything seems in order.
except
your base string has enoauth_consumer_key=dHbWZ6id when it should be
enoauth_consumer_key%3DdHbWZ6id
byebye
r.d.
On Tue, 2010-06-01 at 20:30 -0700,
