Great, now we can home in on the problem.
- Have you verified that in each environment you are testing in that your
clock is within 5 minutes of the clock on api.twitter.com? (Returned in a
Date header for every request).
- I noticed that you're including an oauth_token= parameter in your request
I STILL AM NOT ABLE TO GET THIS DONE
The base url is
POSThttp%3A%2F%2Fapi.twitter.com%2Foauth
%2Frequest_tokenoauth_consumer_key%3DN3jplhm1n1ypCzg2eWEg2w
%26oauth_nonce%3Dkh1282296538%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1282296538%26oauth_version%3D1.0
The signature created
http://oauth.net/core/1.0/#anchor9
This states that the callback parameter will come in for the
Authorization step once the request token is obtained.
Is the doc outdated or am i misinterpreting it?
On Aug 20, 7:19 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
It sounds like your
I read in the documentation example the following.
Authorization: OAuth realm=http://photos.example.net/;,
oauth_consumer_key=dpf43f3p2l4k3l03,
oauth_token=nnch734d00sl2jdk,
oauth_signature_method=HMAC-SHA1,
Yes, it is, and although this is one of the three forms you can use, the
header authorization is preferred.
Tom
On 8/19/10 10:06 AM, Mukha Mudra wrote:
I read in the documentation example the following.
Authorization: OAuth realm=http://photos.example.net/;,
