Thanks for finding that, but twitter still refuses it

basestring:

POST&http%3A%2F%2Fapi.twitter.com
%2Foauth%2Frequest%5Ftoken&oauth_consumer_key%3DdHbWZ6idD9VEuQ5tNUufA%26oauth_nonce%3D6739551275477403%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1275477403%26oauth_version%3D1.0

authorization tag:

Authorization: OAuth oauth_consumer_key="dHbWZ6idD9VEuQ5tNUufA",
oauth_nonce="6739551275477403", oauth_signature_method="HMAC-SHA1",
oauth_timestamp="1275477403", oauth_version="1.0",
oauth_signature="jRYBO%2B1Nh88v3YrJgCGl5vHpAh4%3D"



2010/6/2 Ramy Daghstani <ramy.daghst...@gmail.com>

> 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 "en&oauth_consumer_key=dHbWZ6id" when it should be
> "en&oauth_consumer_key%3DdHbWZ6id"
>
> byebye
>
> r.d.
>
> On Tue, 2010-06-01 at 20:30 -0700, arthurprs wrote:
> > 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:
> >
> > POST&http%3A%2F%2Fapi.twitter.com%2Foauth%2Frequest
> > %5Ftoken&oauth_consumer_key=dHbWZ6idD9VEuQ5tNUufA%26oauth_nonce
> > %3D248256711275449040%26oauth_signature_method%3DHMAC-
> > SHA1%26oauth_timestamp%3D1275449040%26oauth_version%3D1.0
> >
> >
> > authorization tag:
> >
> > Authorization: OAuth oauth_consumer_key="dHbWZ6idD9VEuQ5tNUufA",
> > oauth_nonce="248256711275449040", oauth_signature_method="HMAC-SHA1",
> > oauth_timestamp="1275449040", oauth_version="1.0",
> > oauth_signature="SaG5KExe2frRkFMvZjJqHoZEp%2Bk%3D"
> >
> >
> > Someone can spot the problem?
> > Thanks in advance
> > Arthur.
>
>
>

Reply via email to