didnt work.
i cant believe this is that hard.
PLEASE HELP ME, THIS COMPUTER IS ABOUT TO SLEEP WITH THE FISHES
thanks,
MTCoder
On Sep 14, 5:00 pm, MTCoder sguerr...@gmail.com wrote:
I am away from my work computer so i cant try out this suggestion just
yet but is this what it should look
Spotted some more encoding errors in your example -- on your oauth_token you
are encoding the - character (both in the base string and your
authorization header), which is not a reserved character for these purposes
(see http://oauth.net/core/1.0a/#encoding_parameters ) . What library, if
any, are
still getting the 401
basestring:
POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml
oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26
oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26
oauth_signature_method%3DHMAC-SHA1%26
oauth_timestamp%3D1284487942%26
Your Base String looks fine. Are you using the right keys to sign the
request? Is there any response from the API, except for 401? (Error
message?)
Tom
On 9/14/10 8:14 PM, MTCoder wrote:
still getting the 401
basestring:
POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml
all the keys are the same that use when making calls to get the
timeline.
Steve
On Sep 14, 1:08 pm, Tom van der Woerdt i...@tvdw.eu wrote:
Your Base String looks fine. Are you using the right keys to sign the
request? Is there any response from the API, except for 401? (Error
message?)
Tom
MTCoder:
You've got a little bit of an escaping problem here..
First, spaces aren't valid characters for your POST body. Personally, I
recommend using %20 to represent a space. + would also be valid in a POST
body.
Once your POST body is correct, the escaping for your OAuth signature base
I am away from my work computer so i cant try out this suggestion just
yet but is this what it should look like when i do?
basestring:
POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml
oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26
oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26
