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:

>
>
> 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<HTTP://twitter.com/oauth/request_token%26oauth_consumer_key%0A%3d6RfEXDtG3UBD1JFpUCPtg%26oauth_nonce>
> %3d1246848991%26oauth_signature_method%3dHMAC-SHA1%26oauth_timestamp
> %3d1246848991%26oauth_version%3d1.0
>
> #Signature: (after HMAC-SHA1 encrypted, Base64 encoding and URL
> encoding)
>     MXMwzBjqXWuNZrGpYi2OoBS%2bEdY%3d
>
> #HTTP request header I sent: (use GET as the HTTP method,
> HttpSendRequest() )
>     Authorization: OAuth
> oauth_consumer_key="6RfEXDtG3UBD1JFpUCPtg",oauth_signature_method="HMAC-
> SHA1",oauth_signature="MXMwzBjqXWuNZrGpYi2OoBS%2bEdY
>
> %3d",oauth_timestamp="1246848991",oauth_nonce="1246848991",oauth_version="1.0"
>
>
> On Jul 3, 10:19 pm, Abraham Williams <4bra...@gmail.com> wrote:
> > Based onhttp://
> apiwiki.twitter.com/Twitter-REST-API-Method%3A-oauth-request_t...
> > should be using a GET.
>



-- 
Internets. Serious business.

Reply via email to