Though the resource does not require authentication if you're providing malformed or invalid auth credentials to the method, there are times when we will evaluate the credentials you provide.
Make sure that your implementation isn't attaching malformed/unsupported/invalid authentication details to methods not requiring auth. For instance, if you're providing an OAuth header with a non-existant oauth_token you may get a failure as we don't support two-legged OAuth. Make sure you aren't sending a basic auth header of any kind. Taylor On Tue, Dec 14, 2010 at 3:20 PM, Tim Chen <t...@evri.com> wrote: > Hi all, > > I'm calling GET /1/users/show.json?screen_name=xxxx in my application > using Apache commons httpclient 4.0 java with oauth-signpost, and I > used to get successful responses back. > > Today I tried it again and I'm now getting 401, and I see that this > request is being challenged with authentication. > > Looking at the docs, it says it needs no authentication. > > I wonder what has changed, or I'm doing something wrong? > > Thanks, > > Tim > > -- > 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
