Thanks for everyone's help on this. I think that I now have this working (twitter documentation values match up).
My problem now is that although I'm confident of my algorithm, twitter is always responding 401. I've debugged my network service and the message being returned is Incorrect Signature. I do not understand how this can be... :S On Mar 15, 6:03 am, kamesh SmartDude <kamesh.smartd...@gmail.com> wrote: > Hai lappynet, > > I Used GET method to retrive the Request Token And I Avoided the OAuth > Callback, because it was registered when i registered my app. > > Below is the method how i am doing. > > ****** SignatureBase String is ***** > > GET&https%3A%2F%2Fapi.twitter.com > %2Foauth%2Frequest_token&oauth_consumer_key%3Dpppppppp > %26oauth_nonce%3DydBxFJKdzK%26oauth_signature_method%3DHMAC-SHA1%26oauth_ti > mestamp%3D1300167727%26oauth_version%3D1.0 > > Signature Key U are appending "&" and it is correct. > > i am adding the oauth header like below > > OAuth realm="Twitter API", oauth_consumer_key=pppppppp, > oauth_nonce=ydBxFJKdzK, oauth_signature=89%2BSoLKBdE%2FeHN5PFRxNl3G7tNo%3D, > oauth_signature_method=HMAC-SHA1, oauth_timestamp=1300167727, > oauth_version=1.0 > > I think u might have some problem with generating the signature. > > Try this, > //kamesh > > > > > > > > On Mon, Mar 14, 2011 at 8:16 PM, lappynet <georgina.hug...@gmail.com> wrote: > > cURL... I've heard about this, but I don't really know about it. Is > > there a windows version as I don't have access to other OSs at work > > (*sigh*)? > > > On Mar 14, 2:18 pm, Taylor Singletary <taylorsinglet...@twitter.com> > > wrote: > > > Hi Georgina, > > > > Everything appears correct with your base string for this step. > > > > Are you performing this operation through a HTTP proxy of any kind? Have > > you > > > tried producing a valid OAuth header and executed it in curl (without > > having > > > "executed it" in C# first)? I'm not familiar with C#'s HTTP request > > > libraries and the configuration options available to you in it. > > > > We were having an issue with occasionally hanging connections recently > > and > > > it's possible that it may be related -- but if that's the case, you > > > shouldn't have it occur to you every time -- it would be one out of X > > times. > > > > I'm curious where the connection is hanging -- while you are sending HTTP > > > request headers or when your HTTP client is awaiting a response? > > > > Thanks, > > > Taylor > > > > On Mon, Mar 14, 2011 at 7:02 AM, lappynet <georgina.hug...@gmail.com> > > wrote: > > > > Hi > > > > > I'm using C#.NET to produce an oob client. I've fallen at the first > > > > hurdle though as I'm failing to make the token request. > > > > > I've gone through many iterations, and am no longer receiving a 417, > > > > 404, or 401. This is very positive! Now my application hangs whilst > > > > waiting for a response from twitter. (I left it running for an hour > > > > over lunch and still nothing happened, and the code didn't appear to > > > > want to step through.) > > > > > I've tried with the values detailed in the documentation to have a > > > > look at the variables that have been produced from them in my > > > > algorithm. I think that I've traced it down to being the way I > > > > generate the signature string: > > > > > string signingKey = Uri.EscapeDataString(ConsumerSecret) + "&"; > > > > HMACSHA1 hasher = new HMACSHA1(new > > > > ASCIIEncoding().GetBytes(signingKey)); > > > > string signatureString = Convert.ToBase64String(hasher.ComputeHash(new > > > > ASCIIEncoding().GetBytes(baseString))); > > > > > My base string is: > > > > > POST&https%3A%2F%2Fapi.twitter.com%2Foauth > > > > %2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%XXX > > > > %26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method > > > > %3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0 > > > > > Any pointers as to where I may be going wrong? > > > > > Thanks in advance > > > > Georgina > > > > > -- > > > > Twitter developer documentation and resources: > >http://dev.twitter.com/doc > > > > API updates via Twitter:http://twitter.com/twitterapi > > > > Issues/Enhancements Tracker: > > > >http://code.google.com/p/twitter-api/issues/list > > > > Change your membership to this group: > > > >http://groups.google.com/group/twitter-development-talk > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
