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 copy and paste that
wrong, so I'll check my code). Also, I'll check the &'s.

On Thu, Jun 4, 2009 at 05:12, Dossy Shiobara <do...@panoptic.com> wrote:

>
> 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
>>    %3Db52968e8-7145-4c91-8066-563d37a1107f%26oauth_signature_method
>>    %3DHMAC-SHA1%26oauth_timestamp%3D1244001043%26oauth_token%3D
>>    %26oauth_version%3D1.0
>>
>
> If that is truly what you're signing, there are two problems I see:
>
> 1) You are URI-encoding the ampersand separator ("&" -> "%26").  Don't.
>
> 2) You have the method and URL in the signature string twice.  Don't.
>
> Those are the immediate problems I see, anyhow.
>
> --
> Dossy Shiobara              | do...@panoptic.com | http://dossy.org/
> Panoptic Computer Network   | http://panoptic.com/
>  "He realized the fastest way to change is to laugh at your own
>    folly -- then you can let go and quickly move on." (p. 70)
>



-- 
Internets. Serious business.

Reply via email to