Hi Matt, I have fixed a bunch of the formatting issues and it now validates in the OAuth tester app that Tom posted, but I am still getting an error when posting.
Here is my updated request string. POST&https%3A%2F%2Fapi.twitter.com%2Foauth %2Frequest_token&oauth_consumer_key%3DXXXXXXXXXXXXX%26oauth_nonce %3D430489.541778%26oauth_signature_method%3DHMAC %2DSHA1%26oauth_timestamp%3D1297274801%26oauth_version%3D1.0 Here is the error returned. Failed to validate oauth signature and token Here is the return header. HTTP/1.1 401 Unauthorized Connection: close Expires: Tue, 31 Mar 1981 05:00:00 GMT Date: Wed, 09 Feb 2011 18:06:45 GMT Server: hi X-Runtime: 0.00454 Vary: Accept-Encoding X-Transaction: Wed Feb 09 18:06:45 +0000 2011-87785-54083 Pragma: no-cache Status: 401 Unauthorized Cache- Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: k=[MY IP ADDRESS].1297274805118711; path=/; expires=Wed, 16-Feb-11 18:06:45 GMT; domain=.twitter.com Set-Cookie: guest_id=129727480520719350; path=/; expires=Fri, 11 Mar 2011 18:06:45 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCNibmgsuAToHaWQiJTYwMDg4OGQ2N2ZlMTBm %250AY2I1NWFiNGRmNWRiY2I2N2UxIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--0e5cbcd15c652517645f3fb4a648abeabec997e9; domain=.twitter.com; path=/; HttpOnly X-Revision: DEV Last-Modified: Wed, 09 Feb 2011 18:06:45 GMT Content-Type: text/html; charset=utf-8 Any further ideas? -Dale On Feb 8, 5:34 pm, Matt Harris <thematthar...@twitter.com> wrote: > Hi Dale, > > There are a number of things that can cause OAuth to fail. We've clarified > our error messages to try and make it easier to know which bit is the cause > of the problem. > > For timestamps we return the error message "Timestamp out of bounds". > In your case the error message is saying your signature is incorrect. This > means either your basestring is incorrectly encoded, badly formatted or > doesn't match the API request URL and parameters you are sending. > Looking at your basestring I notice that you have a lot of additional > encoding going on and are missing the first & between POST and http. > > To help you get it right I recommended checking out our authentication > overview page on our developer resources site. Specifically the section on > signing requests and acquiring a request token: > http://dev.twitter.com/pages/auth#signing-requests > http://dev.twitter.com/pages/auth#request-token > > Best, > @themattharris > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > > > > > > On Tue, Feb 8, 2011 at 3:58 PM, Dale <d...@dealflow.com> wrote: > > I just set the system clock on my Win 2003 server to net time / > > setsntp:"0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org" as I saw a lot > > of folks saying this fixed their issues, but it had no effect. > > > On Feb 8, 3:15 pm, Dale <d...@dealflow.com> wrote: > > > I am attempting to set up a ColdFusion script to do auto updates to > > > Twitter when a new article is posted to our CMS. I have been having > > > trouble getting the request token and keep getting the Failed to > > > validate oauth signature and token error message when making > > > attempts. > > > > Here is my request string... > > > POSThttp%3A%2F%2Fapi%2Etwitter%2Ecom%2Foauth%2Frequest%5Ftoken%26oauth > > > %5Fconsumer%5Fkey%XXXXXXXXXXXXXXX%26oauth%5Fsignature%5Fmethod%3DHMAC > > > %2DSHA1%26oauth%5Ftimestamp%3D1297206414%26oauth%5Fversion > > > %3D1%2E0%26oauth%5Fnonce%3D556979%2E9534 > > > > I have verified that the time stamp is the the correct epoch time in > > > my time zone (PST). Any help would be appreciated. > > > -- > > 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
