Update: It works now. Thanks to everyone who tried to help me diagnose
the issue.
Today, Hedley posted about the system being off can cause the request
token to fail. This was my exact problem it turns out.
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/aadee92bc5c34
No. According to the oauth spec, your signature key is always
"consumer_secret&token_secret", even if token_secret is empty, so when you
first call request_token, your key will be "consumer_secret&"
On Thu, Jul 9, 2009 at 21:24, Blaine Garrett wrote:
>
> Hi,
>
> Thanks for the quick reply Matt.
Hi,
Thanks for the quick reply Matt. Below is a recap of the setup with a
bit more clarity as well as the keys, url, and pre-encoded data.
Hopefully this sheds some light on the issue. I also tried the PHP lib
someone recommended with the same results - i.e 401 error. So again, I
am thinking it
Hi Blaine,
Failing the validate the signature when getting a request token
is pretty rare. As you said the fact this all works from other
libraries seems to point to a library issue. The most helpful things
to see in these cases are:
• The actual HTTP request and response that fails