Hang on, we think we found something....stop digging for a bit. :)

On May 21, 12:11 pm, DWF <dwfr...@pivotallabs.com> wrote:
> Just tried removing the source param and we still get the 'incorrect
> signature' error.
>
> Twurl from the command line is just fine.
>
> Digging further...
>
> --dwf
>
> On May 21, 11:54 am, Taylor Singletary <taylorsinglet...@twitter.com>
> wrote:
>
>
>
> > Hi DWF,
>
> > AT first glance there doesn't seem to be anything wrong here that I can see.
> > I do see that you're including a source parameter, which isn't necessary
> > when you are POSTing a status update -- Twitter will just use your
> > registered application name from your client application record for that.
>
> > What happens when you try the same call without a source parameter? Curious
> > if we're just throwing a lame error here.
>
> > Taylor Singletary
> > Developer Advocate, Twitterhttp://twitter.com/episod
>
> > On Fri, May 21, 2010 at 11:34 AM, DWF <dwfr...@pivotallabs.com> wrote:
> > > We're having lots of success with OAuth now, which is great.  So far
> > > it looks like all our GETs are working just fine.  And some of our
> > > POSTs - but not all.
>
> > > Here's a POST that works (deleting a user's tweet):
>
> > > url:https://api.twitter.com/1/statuses/destroy.json
>
> > > parameters: {"id": 12532480661}
>
> > > Base String:
> > > POST&https%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fdestroy.json&id
> > > %3D12532480661%26oauth_consumer_key%3D-----%26oauth_nonce
> > > %3D1274466742322abc143248%26oauth_signature_method%3DHMAC-
> > > SHA1%26oauth_timestamp%3D1274466742%26oauth_token%3D-----
> > > %26oauth_version%3D1.0
>
> > > AuthHeader:
> > > Authorization = OAuth oauth_signature_method="HMAC-SHA1",
> > > oauth_nonce="1274466742322abc143248", oauth_timestamp="1274466742",
> > > oauth_consumer_key="-----", oauth_version="1.0", oauth_token="-----",
> > > oauth_signature="mg23Yowg9Y40imqcOH9SibMHSHE%3D"
>
> > > And here's one that's NOT working (updating a status):
>
> > > url:https://api.twitter.com/1/statuses/update.json
> > > parameters: {"source": "tweed", "status": "Tweet"}
>
> > > BaseString:
> > > POST&https%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
> > > %2Fupdate.json&oauth_consumer_key%3D-----------%26oauth_nonce
> > > %3D1274466366892abc252116%26oauth_signature_method%3DHMAC-
> > > SHA1%26oauth_timestamp%3D1274466366%26oauth_token%-------------
> > > %26oauth_version%3D1.0%26source%3Dtweed%26status%3DTweet
>
> > > AuthHeader:
> > > Authorization = OAuth oauth_signature_method="HMAC-SHA1",
> > > oauth_nonce="1274466366892abc252116", oauth_timestamp="1274466366",
> > > oauth_consumer_key="--------", oauth_version="1.0",
> > > oauth_token="---------", oauth_signature="V4HjQU7%2BTYF2MFtkkR7T8OYM54Q
> > > %3D"
>
> > > The error we get is:
> > > {
> > >  status: 401,
> > >  responseText: {"request":"/1/statuses/
> > > update.json","error":"Incorrect signature"}
> > > }
>
> > > Thoughts?

Reply via email to