OK, finally I got my code to work.
The problem was in how I registered application on Twitter, and not in
my code.
1) Register application as a Browser, not as a Client one;
2) Register callback URL used in application.
Can't think of any reason first setting differs in meaning from other
Hi Taylor, thanks for your reply.
1) No, clock is pretty much synced. I've come across this advice
already and checked it in first place:
my oauth_timestamp is 1280250833
and the server responds with header X-
Transaction=1280250931-50619-29066
which I suppose includes server-side clock. The
Hi Taylor,
Thank you for your prompt reply.
Yes, I'm typically not sending oauth_callback in query string. I
adapted my example so that it produces exactly the same digest string
as tool on hueniverse.com site does.
If I remove these parameters from query string and add oauth_callback
to
I would just greatly appreciate if anyone could post here complete
request which authenticates on Twitter.
BTW, some sites (e.g., habrahabr.ru or hyves.nl mentioned above) print
some useful debug info in their response if authentication fails.
E.g., they first dump unescaped parameters they
OK, I just substituted sample OAuth parameters found here
http://dev.twitter.com/pages/auth
to my application, and I get exactly the same oauth_signature string:
key=MCD8BKwGdgPHvAuvgvz4EQpqDAtx89grbuNMRd7Eh98
text=POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
