I followed the whole oAuth chain to aquire an accesstoken for my
application:
Call 1:
sent:
https://api.twitter.com/oauth/request_token?oauth_consumer_key=[mykey]&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1293014232&oauth_nonce=OgIwk4&oauth_signature=[signature]
result:
oauth_token=[token]&
Set-Cookie: _twitter_sess=VERYLONGSIGNATUREacbd; domain=.twitter.com;
path=/
Does that mean the the Authorization did not come through, since the
WWW-Authenticate says Basic?
On 22 dec, 14:50, Cujo wrote:
> I followed the whole oAuth chain to aquire an accesstoken for my
> application:
> Call
No, the search term does not contain any escapable characters. I ruled
that out allready as the source for "incorrect signature"
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://