You can't just send a header that's placed on a website - the
timestamp is old (127xxx series = VERY old) and the values used in the
request were most likely fake.
What I meant is that you should feed the values on that page into your
class/library, and then check whether oauth_signature is the
Hi Tom,
Thanks for your email back..
I managed to get it sorted in the end.. Not entirely sure since I was cursing
quite a bit, but hopefully by the end of today I'll have a full REALStudio
(REALBasic) oAuth class..!
Thanks
Andy
On 31 Jul 2010, at 01:50, Tom wrote:
I don't immediately
I don't immediately see what's wrong, but consider tracing your steps.
You already have a class that creates the authorization header. Feed
it some information which you know to be correct, and check for the
outcome.
You could use these: http://dev.twitter.com/pages/auth#request-token -
all
Just going to chime in that I'm having the same problem with my own
implementation, despite following the documentation exactly. Even
sending the exact header that Tom linked to, OAuth
oauth_nonce=QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk,
oauth_callback=http%3A%2F%2Flocalhost%3A3005%2Fthe_dance
You can use one of the many libraries for most of the more popular
languages(and some for the less popular), or you can create your own library
to communicate to the API.
Ryan
On Thu, Nov 12, 2009 at 3:09 AM, albana tejashree1@gmail.com wrote:
Hi everybody!
I am about to develop a
no need to chase changes if you take a dependency on a solid library.
∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera
On Thu, Nov 12, 2009 at 2:37 PM,
There are two broad types of Twitter APIs: authenticated and
non-authenticated. The type is mentioned in the API docs.
If your application is lucky enough to need only non-auth APIs then all you
need to do is make HTTP requests and parse the result, in your favourite
language.
Authenticated APIs
