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}
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
I think you have the same problem I posted about yesterday. In your base
string the '%' chars of the status are supposed to also be escaped. Here is
an example from my app
My status update string
timestamp:1274472570 Rejoice! I am done debugging :-).
POSThttp%3A%2F%2Fapi.twitter.com
quickly one more thing, i twould also be cool to get some more details about
what exactly went wrong when the server side validation of the signature
fails. All you get now is 'Invalid Signature' and there are quite a few
things you could get wrong in developing that signature.
On Fri, May 21,
Mike,
We're going to be a lot more informative on signature generation errors in
the near future -- we have a newer implementation of OAuth 1.0a waiting in
the wings that will provide the signature base string we generated on a
failed request. More details when the staggered release of that is
That will be very helpful. Thanks Taylor.
On Fri, May 21, 2010 at 1:20 PM, Taylor Singletary
taylorsinglet...@twitter.com wrote:
Mike,
We're going to be a lot more informative on signature generation errors in
the near future -- we have a newer implementation of OAuth 1.0a waiting in
the
