SOLVED!
The moral of the story is to keep your nonce values SIMPLE.
We were generating a random value:
Base64.encode('1:' + counter++ + ':' + random + Date.now());
which most of the time resulted in a string that contained an equals
sign character, which then gets urlencoded to %3D.
It appea
Taylor: Here's what we're sending now. The signature looks like the
correct length. But we're getting the same error.
POST /oauth/access_token HTTP/1.1
Host: api.twitter.com
Authorization: OAuth oauth_signature_method="HMAC-SHA1",
oauth_nonce="MToxOjQyOTY0NzEyNzM3MDMzMzQwMTU%3D",
oauth_timestam
It turns out that we have a base64 encoding problem, which means our
signature actually is bad.
Working on it now.
--dwf
On May 12, 1:06 pm, DWF wrote:
> We just coded up a simple Ruby script to make the same request,
> building our post body by hand into a string to ensure the escaping
> (or n
We just coded up a simple Ruby script to make the same request,
building our post body by hand into a string to ensure the escaping
(or not) of the params.
So we know that going into Net::HTTP the underscores are underscores
and NOT %5F's.
Same response from the server.
--dwf
On May 12, 11:14
