Hi there, We're now a bit stricter with how we evaluate the validity of requests.
Few things to look into for starters -- hopefully will help you discover the subtle issue: - Are you setting your Content-Type: x-www-form-urlencoded when POSTing any kind of POST data? - Make sure that your signature basestring is properly sorting your parameters and that any param values requiring percent-encoding are properly encoded. If your POST body contains any characters that need to be %-encoded, they'll need to be %-encoded again for your signature base string - Double verify that your consumer key and secret are correct and being used at the right steps. - Double verify that you're specifying an oauth_token for resource requests and that you've signed the request with the composite signing key made up of your consumer secret and the access token secret, joined by a "&" character. - If you're using header based auth, make sure that you aren't sending oauth_* parameters in multiple locations like the query string in addition to the header Thanks, @episod <http://twitter.com/intent/user?screen_name=episod> - Taylor Singletary On Wed, Jun 15, 2011 at 1:20 PM, @giberti <erik.gibe...@gmail.com> wrote: > A few months ago I wrote an application that interfaced with two API > calls: statuses/user/timeline and statuses/update. It has been working > fine until about seven days ago when I started receiving 401 status > codes when reading the user timeline. > > I'm using a hand rolled OAuth / Twitter library that I built using the > examples provided on the developer docs. I'm not sure where to go from > here. > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
