Similar to Tim's suggestion, I'd also check out
http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html ...
shows step by step conversion values which you can use to pinpoint
where your library might be having problems.
On Jun 3, 10:27 pm, Tim timot...@gmail.com wrote:
Maybe this
On 6/4/09 12:07 AM, JDG wrote:
My signature base string for that looked like:
GET%26http%3A%2F%2Ftwitter.com%2Foauth%2Frequest_token%26GET%26http%3A
%2F%2Ftwitter.com%2Foauth%2Frequest_token%26oauth_consumer_key
%3D9CCTnLpstYI8RIxGE7yhQ%26oauth_nonce
Thanks everyone! I will try all these suggestions
1. The hueniverse guide is where I got started. It's actually incredibly
useful.
2. I will definitely try the explorer.
3. Thanks, Dossy! I've been staring at those for so long that I didn't see
the multiple GETs (I'm almost positive that I didn't
On Tue, Jun 2, 2009 at 22:53, @jigglyonee ghil...@gmail.com wrote:
I'm passing, hopefully, the correct parameters. A typical query string
looks like this:
That's the whole point, though. I'm still at the point where I'm trying to
*get* an oauth token.
On Thu, Jun 4, 2009 at 13:51, Abraham Williams 4bra...@gmail.com wrote:
On Tue, Jun 2, 2009 at 22:53, @jigglyonee ghil...@gmail.com wrote:
I'm passing, hopefully, the correct parameters. A
I know it's rather gauche to bump one's own posts, but I'm unfortunately at
a bit of a standstill here. Can any of the Twitter developers let me know if
there is a way to retrieve more detailed error information from a given HTTP
response? Thanks!
On Tue, Jun 2, 2009 at 21:53, @jigglyonee
Maybe this OAuth Explorer would help you checking the different step
and the parameters of your query:
http://sevengoslings.net/~fangel/oauth-explorer/
Also, you might want to try an existing OAuth library in parallel with
yours to see that it works the same. (even though you apparently tried
