Dear Tom,

 its is in sorted order only. And moreover the same order working fine
in Simualtor

On Sep 1, 9:37 pm, Tom van der Woerdt <i...@tvdw.eu> wrote:
> You should sort the fields in the Base String.
>
> Tom
>
> On 9/1/10 6:35 PM, Karthik wrote:
>
> > Dear Taylor,
> >  I am developing an twitter app in MTK (Mediatek platform and my app
> > has the x-auth privilages)
> > My Issue:
> >  I am getting  errocode 401 (Failed to validate oauth signature and
> > token), only in the mobile (MTK - media tek - where I am not using
> > proxy).
> >  I ma getting the x-auth access token and all other api's are working
> > fine in the simualtor (where I am using proxy)
>
> > So when I look in to the TCP packets :
> > In simulator:
> > POST https:api.twitter.com/oauth/access_token HTTP/1.1 (Absolute URL)
> > Host: api.twitter.com
> > authorization: OAuth oauth_consumer_key="abcdefghijklm",
> > oauth_nonce="1262304257", oauth_signature_method="HMAC-SHA1",
> > oauth_timestamp="1262304256", oauth_version="1.0",
> > oauth_signature="4vvYMzqy1BBixGRh4bpeA5xa%2BPo%3D"
>
> > but in target I ma getting as :
> > POST /oauth/access_token HTTP/1.1  (Relative URL)
>
> > Other than this , no other changes I have found between simulator and
> > target.
>
> > My Signature simple string :
>
> > POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> > %2Faccess_token&oauth_consumer_key%abcdefghijklm%26oauth_nonce
> > %3D1262304257%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> > %3D1262304256%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
> > %26x_auth_password%3Dtest1234%26x_auth_username%3Dnareshs
> > %2540google.com
>
> > I am using the platform provided sha1-hmac algorithm which is same in
> > target and simulator.
>
> > Please help me find out the issue which is only occuring in my target.
>
> > Regards,
> > Karthik

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Reply via email to