Hi Carl,

My immediate response is that the order of arguments in your basestring are
different to the order in your authorization header. This would cause the
signatures to be different as you signed them in one order but delivered in
another.

See if keeping them in the same order fixes it.

Matt

On Wed, Jun 30, 2010 at 2:29 PM, cthress <c...@4thress.com> wrote:

> Matt,
>
> Here's the base string:
> GET&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
> %2Fretweeted_by_me.json&oauth_consumer_key%3D****************
> %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> %3D1277932576%26oauth_token%3D****************%26oauth_version%3D1.0
>
>
> And here are the headers:
> Authorization: OAuth realm="http%3A%2F%2Fapi.twitter.com
>
> %2F",oauth_version="1.0",oauth_nonce="e32167a3bfc33f59e1d18e3907df5ee6",oauth_timestamp="1277932576",oauth_consumer_key="*********",oauth_token="*****************",oauth_signature_method="HMAC-
> SHA1",oauth_signature="ZQZvWpefFlWr1ro%2FxMF%2FNvCX624%3D"
>
>
> Let me know if you need any of the values I replaced with asterisks.
>
>
> Thanks,
>
> Carl
>
>
> On Jun 30, 3:35 pm, Matt Harris <thematthar...@twitter.com> wrote:
> > Hi Carl,
> >
> > Could you share your base string and the post headers you are sending?
> (with
> > the oauth token and secret obscured) and we'll see what we can find.
> >
> > Thanks,
> > Matt
> >
> > On Wed, Jun 30, 2010 at 1:10 PM, cthress <c...@4thress.com> wrote:
> > > Matt,
> >
> > > I'm running into a different issue now. I'm using the same method for
> > > authentication as I would for user_timeline, but I'm getting an
> > > "incorrect signature" error returned to me when I try authenticating.
> > > When I run the same function with user_timeline as the endpoint, it
> > > works great. Any ideas?
> >
> > > Thanks,
> >
> > > Carl
> >
> > --
> >
> > Matt Harris
> > Developer Advocate, Twitterhttp://twitter.com/themattharris
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

Reply via email to