I still don't see your status in the query string of the URL.  I see it in
string for the signature, but in your actual URL, it's not there.

This is my entire URL when posting a status update:


notice how my "status" is a query string parameter also.  I don't see that
in yours.


On Tue, Jan 26, 2010 at 12:50 PM, eco_bach <bac...@gmail.com> wrote:

> Ryan
> Still 'Incorrect signature'
> Here's my BASE signature query string BEFORE % encoding (NOTE all
> SORTED and asterisks for my consumer key!)
> oauth_consumer_key=********&oauth_nonce=16EAFA36-2A91-32A5-4A5C-6BB80EF9B45B&oauth_signature_method=HMAC-
> SHA1&oauth_timestamp=1264527609&oauth_token=9353572-
> G8h52Icbe0cjWIMl59fepUofRxoHzHznhzEwo9oqI&status=having some fun
> getting OAuth and the Twitter api working
> This is my final request URL, the %253D at the end of my signature
> looks suspect, doubly encoded? But pretty sure worked with verify
> credentials
> request.url==http://www.bitstream.ca/twitter/proxy.php?path=http%3A%2F
> %2Ftwitter.com%2Fstatuses%2Fupdate.json%3Foauth_consumer_key
> %3D****************%26oauth_nonce
> %3D16EAFA36-2A91-32A5-4A5C-6BB80EF9B45B%26oauth_signature_method
> %3DHMAC-SHA1%26oauth_timestamp%3D1264527609%26oauth_token%3D9353572-
> G8h52Icbe0cjWIMl59fepUofRxoHzHznhzEwo9oqI%26oauth_signature
> %3D5QuhEDae4gZHAxel8JVwLwkQ5J4%253D

Reply via email to