[twitter-dev] Re: Incorrect Signature for oAuth

2010-06-08 Thread rhysmeister
Thanks to all your replies helped I can now perform status updates via oAuth. I'm rather irritated that Uri.EscapeDataString doesn't escape all illegal characters. It just fails now if a status update contains exclamation marks, asterisk, dollar signs, single quotes and probably a few more. I'll

[twitter-dev] Re: Incorrect Signature for oAuth

2010-06-07 Thread StephenBnz
Hi Rhys, - you're right status should be at the end of the base string. Even though it's sent as a POST, it still has to go in alpha order in the base string. - Also be careful of the leading %3F you've got after the update.xml - should just be (method)&(baseURL+service)&(list of params separated b

[twitter-dev] Re: Incorrect Signature for oAuth

2010-06-07 Thread rhysmeister
Hi, thanks to you both. I've removed the source parameter. There is something wrong with my signature base indeed. Here's what I am sending for a status update... POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml&%3Fstatus %3Dtest%26oauth_consumer_key%3Dxx%26oauth_

Re: [twitter-dev] Re: Incorrect Signature for oAuth

2010-06-07 Thread Taylor Singletary
To help you debug, it would be useful to see the signature base string that was generated for the request. Possible things going wrong: the signature base string isn't mentioning that this is a POST, or your OAuth-based parameters are leaking into your POST body.. As Hwee-Boon said, you also needn

[twitter-dev] Re: Incorrect Signature for oAuth

2010-06-06 Thread Hwee-Boon Yar
Since it's GET works and POST, no. 1 reason is to make sure the base URI in the base signature string is constructed correctly. In your example, you don't need source= since it's OAuth. -- Hwee-Boon On Jun 6, 8:56 pm, rhysmeister wrote: > Hi All, > > I am having problems identifying what is