I'm having the same issue with my client.

Debug information:
URL: http://api.twitter.com/1/statuses/home_timeline.json
Oauth Token: 6339722-C6ciVM1DS5dsbezoxX25K2DM0LDysexMD0QDm28s
Oauth Token Secret: XRLC2XcJ1gpPd3qyOHR9szIWs1OXMOkY3NljpM36Vo
Consumer Key: CabFljpBvebzTnWpsUtw
Consumer Secret: what_is_on_my_app_page
Nonce: 88c65140bb4caeb02264c1c02dcd5e3a44c1e7cb
Time: 1277241300
Version: 1.0
Signature: FuB86c97j9VBnbC7JmJzqbRwBOQ%3D

I'll see what I can do about providing you any more information you may require.

(Demonicpagan on Twitter)

On 6/22/2010 1:12 PM, Tom wrote:
Hi all,

I'm trying to write a simple Twitter client but so far I'm not making
a lot of progress.

I already got as far as retrieving the timeline, but I seem to be
unable to sign the request. When I re-calculate the signature with a
different application, it's exactly the same. Yet Twitter reports that
it's wrong! ("Incorrect signature" with a 401 error)

Of course, I'm using a proper secret and not the one below, but that
one was used to calculate the signature for the request below.

Can anyone confirm that I'm using the proper signature? Information is

Debug information :
URL: http://api.twitter.com/1/statuses/home_timeline.json
Token: 18911703-HjjtYklryN9C99pfTiXWs52PvEqrfabluLCdh5IJU
Customer key: QetEw0FtIfvaNyBfgxRYmw
Secret: this_has_been_used_as_the_secret
Nonce: jOzrZNZtsGFLftfjJpdiOfjYtgvNFzWPPXIOKHKE
Time: 1277230019
Version: 1.0

Signature: aiUvshdfeRz2Z6G6a9DkYDbXJEc=
Str1: GET&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
Str2: OAuth oauth_signature="aiUvshdfeRz2Z6G6a9DkYDbXJEc%3D",
oauth_version="1.0", oauth_signature_method="HMAC-SHA1",
oauth_timestamp="1277230019", oauth_token="18911703-
No post body.


This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. E-mail transmission cannot be guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. The sender therefore 
does not accept liability for any errors or omissions in the contents of this 
message, which arise as a result of e-mail transmission.

Reply via email to