Thanks a lot!
After fixing this upper case issue and I also found there is a
misunderstanding about base string URL encoding, the request token can
be returned now.
Thanks everyone ~
On Jul 6, 1:04 pm, JDG ghil...@gmail.com wrote:
from the oauth core section on parameter encoding:
Thanks~
I've also tried GET method, however, it still returned same message.
The following is the data:
#Base String:
GET%26HTTP://twitter.com/oauth/request_token%26oauth_consumer_key
%3d6RfEXDtG3UBD1JFpUCPtg%26oauth_nonce
%3d1246848991%26oauth_signature_method%3dHMAC-SHA1%26oauth_timestamp
from the oauth core section on parameter encoding:
Hexadecimal characters in encodings MUST be upper case.[1]
Your string has %2b and %3d. You should see if that's causing it.
[1] http://oauth.net/core/1.0/#signing_process
On Sun, Jul 5, 2009 at 21:01, muramastu keic...@gmail.com wrote:
Based on
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-oauth-request_tokenyou
should be using a GET.
On Fri, Jul 3, 2009 at 04:58, muramastu keic...@gmail.com wrote:
Dears,
I'm trying to write a win32 desktop application to access
twitter.com by using C++ and stopped at the 1st
