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 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",
> oauth_nonce="OAUTH389651810F52376E300436587FC78694"
>
> I have tried testing using the netflix oauth tester and that also
> fails with a 401
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to