@Taylor:
This isn't the API itself, this is OAuth. request_token is definitely
two-legged
@Steven:
Your header looks fine, the values are properly URL encoded and the time
appears to be valid. To help you debug this issue, we need to know the
Base String you are testing with, the request you
Hi Steven,
I don't see an oauth_token in this header -- all authentication-requiring
OAuth-based requests with the Twitter API are 3-legged and require an
oauth_token to represent the user.
Taylor
On Wed, Dec 15, 2010 at 2:11 PM, Steven Neiland <
steven.sterlingmarket...@gmail.com> wrote:
> Can
Can anybody see why the following authorization header would return a
401 when trying to get a request token?
OAuth oauth_signature="UlAaUlR5A5uJfCcz%2FUVJl53aRy4%3D",
oauth_timestamp="1292450596", oauth_signature_method="HMAC-SHA1",
oauth_version="1.0", oauth_consumer_key="w50vPfRyCVgzBxtdAsoxwg"
