I'm getting CC'd on all these emails, can you take me off please?
Sent via BlackBerry by AT&T
-----Original Message-----
From: Matt Harris <thematthar...@twitter.com>
Sender: twitter-development-talk@googlegroups.com
Date: Tue, 8 Feb 2011 17:34:18
To: <twitter-development-talk@googlegroups.com>
Reply-To: twitter-development-talk@googlegroups.com
Subject: Re: [twitter-dev] Re: Failed to validate oauth signature and token
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, Twitter
http://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
--
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
