On 09/23/10 03:03, SJM wrote:
Hi there,
I was wondering if anyone has had success in accessing Twitter using
liboauth (the C library). I have been able to authenticate against the
Twitter Oauth API, but when I want to send a status message I get a
signing error.
HTTP-reply: ?xml version=1.0 encoding=UTF-8?
hash
request/statuses/update.xml?
oauth_consumer_key=xamp;oauth_nonce=WR5oK1s9HxdZhM2ugZ95amp;oauth_signature_method=HMAC-
SHA1amp;oauth_timestamp=1285189327amp;oauth_token=xamp;oauth_version=1.0amp;status=128518924112851893121285189313TESTamp;oauth_signature=aDRA99d2CY55gjL7kU1X
%2FaneqtQ%3D/request
errorIncorrect signature/error
/hash
I (triple) checked all my keys and secrets and the order of items in
the request matches that in the signing URL. liboauth all works for
the authentication, but the Twitter 'service' API just can't seem to
agree with me with regards the signature.
I suspect that it may be related to UTF-8 encoding. Is there something
I need to set in the HTTP header for this?
Any help would be most appreciated,
we did figure this out off-list: but for future reference:
On 09/25/10 06:52, Stan Malachowski wrote:
Yes - a typo. http://api.twitter.com/statuses/update.xml works, but
http://api.twitter.com/1/statuses/update.xml is in the Twitter docs.
Your lib works fine. If I had done the POST in the first place I
would have saved a couple of days.
Stan
robin
--
You received this message because you are subscribed to the Google Groups
OAuth group.
To post to this group, send email to oa...@googlegroups.com.
To unsubscribe from this group, send email to
oauth+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/oauth?hl=en.
