Yes, you could assume your signature creation is correct for most API calls.
 However, as you see with the update status API call, it has the extra
parameter that is the status.

Ryan

On Tue, Jan 26, 2010 at 1:46 PM, ryan alford <ryanalford...@gmail.com>wrote:

> Don't do the POST request data.  You do that for Basic Auth, but not for
> OAuth.
>
> Ryan
>
>
> On Tue, Jan 26, 2010 at 1:44 PM, eco_bach <bac...@gmail.com> wrote:
>
>> Ryan
>> Since its a POST its part of my request.data.
>>
>> Didn't think I also needed as part of my query string but will try.
>>
>>
>> Do you know if there is an official Twitter Oauth test page  like
>>
>> http://developer.netflix.com/resources/OAuthTest
>> or Google's?
>> http://oauth.googlecode.com/svn/code/javascript/example/signature.html
>>
>> Tried both and getting a different signature value, so my next
>> question is
>> If I receive information back on verify credentials (and no 'incorrect
>> signature' error), am I safe to assume my signature generation is
>> corect?
>>
>
>

Reply via email to