Dear all,

I have a problem using the Twitter-API with my own OAuth library. My
own efforts to solve this problem led to nothing :-/.

I successfully obtained an oauth_token and an oauth_token_secret via
api-call. I was also possible to send signed GET requests (without
parameters) and i was able to access protected statuses ( i.e.
http://twitter.com/statuses/show/<id>.xml ).

But I failed to send POST requests with additional api-parameters. My
request looks like:

-------------------------------
POST /statuses/update.xml HTTP/1.1
Authorization: OAuth realm="http://twitter.com/statuses/
update.xml",oauth_consumer_key="faVMWtJvXP0IB3wsBaJTQ",oauth_nonce="3e3b26909fa40c2caac60614402a2214",oauth_signature_method="HMAC-
SHA1",oauth_timestamp="1260449888",oauth_token="38161975-15hllTYOlXkOE4jM3wkEzfNkc1qJ0dFxpiXrwGXcB",oauth_version="1.0",oauth_signature="%2F3772JshuQJKDclbDyytiOZ5E3c
%3D"
Host: twitter.com
Content-Length: 16
Content-Type: application/x-www-form-urlencoded
Content-ID: <>
Date: Thu, 10 Dec 09 13:58:08 +0100

status=freutsich
-------------------------------

The signature was constructed from the following signature-base-
string:

POST&http%3A%2F%2Ftwitter.com%2Fstatuses
%2Fupdate.xml&oauth_consumer_key%3DfaVMWtJvXP0IB3wsBaJTQ%26oauth_nonce
%3D3e3b26909fa40c2caac60614402a2214%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1260449888%26oauth_token
%3D38161975-15hllTYOlXkOE4jM3wkEzfNkc1qJ0dFxpiXrwGXcB
%26oauth_token_secret%3DREPLACEDREPLACEDREPLACED%26oauth_version
%3D1.0%26status%3Dfreutsich

I have no idea what i did wrong. I have a suspicion that my failure
had something to do with the additional parameter (status=) and the
way I
add this parameter to the signature-base string ...

Best regards

Julius

Reply via email to