Thanks Taylor. I changed that and base string is now like this POST&%3A%2F%2Fapi.twitter.com%2Foauth %2Frequest_token&oauth_consumer_key%3D************************* %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1282189027%26oauth_nonce%3Dkh432142249
I call the url with query parameters according to the Jane example provided in Appendix of documentation. http://api.twitter.com/oauth/request_token?oauth_consumer_key=*****************************&oauth_signature_method=HMAC-SHA1&oauth_signature=wh6iEO8ch2VdNlccsRQYjs8xFOU&oauth_timestamp=1282189027&oauth_nonce=kh432142249 But now i get "401 Unauthorized" I have checked my consumer key and secret key.They seem to be alright.What could be happening? Should open another post for this? On Aug 19, 12:17 am, Taylor Singletary <[email protected]> wrote: > There are many elements to Twitter, the API, and the stack the runs the > whole site. It is possible, though rare, that you'll see this error in other > conditions. > > Looking at your signature base string here, I notice that you don't include > a separator between the URL you are executing and the parameters -- that > first %26 you have in your signature base string shouldn't be encoded.. it > should just be "&" as it works as a separator between portions: > > $HTTP_METHOD + "&" percent_encoded($REQUEST_URI) + "&" > percent_encoded($URL_ENCODED_PARAMETERS) > > Taylor > > On Wed, Aug 18, 2010 at 12:03 PM, Tom van der Woerdt <[email protected]> wrote: > > > > > On 8/18/10 8:24 PM, Mukha Mudra wrote: > > > Hi All, > > > I just began to connect a Symbian application to Twitter via > > > the REST API. > > > > The base URL used in signature is as follows > > > POST&%3A%2F%2Fapi.twitter.com%2Foauth%2Frequest_token > > > %26oauth_consumer_key%3D*************************** > > > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp > > > %3D1282155396%26oauth_nonce%3Dkh511263264 > > > > In response i get the Twitter Over Capacity html page. > > > > Since I have just begun , I am not sure that apart from server > > > overloading , by any chance, does a wrong invocation of the API also > > > gives this error. > > > > Regards > > > Biju > > > It does not. > > > Tom
