http://dev.twitter.com/pages/auth, section Signing Requests, states :
Then, you take all query parameters and POST body parameters (when the POST
body is of the URL-encoded type, otherwise the POST body is ignored),
including the OAuth parameters necessary for negotiation with the request at
You most likely forget to include in_reply_to_status_id in your Base String.
Tom
On 9/21/10 10:38 PM, Tzanko wrote:
Hello,
When I post to statuses/update with in_reply_to_status_id parameter, I
get Incorrect signature.
However, statuses/update works fine when in_reply_to_status_id is
Can you share what the various states are in your request?
To save some time, here's an example of a few steps of updating a
status in this way. This example replies to tweet 23241674011 with the
status @oauth_dancer test
Signature Base String
Great - works now! Thank you very much!
I am wondering why such 'intricacies' are not mentioned in the
documentation. I mean, how can one figure out the the optional
parameter in_reply_to_status_id has to come in front of the oauth
parameters in the base string? Or maybe there is some sort of a
