I've gotten 401's as well...but this doesn't return a 401, it's
returning a valid response...just not what I'm requesting! :O

I DO get 401's when I don't include the port (:9000) in the URL though
(or when I build the Authorization header like on dev.twitter.com...or
in the Twurl console).

Thanks! :)

On Mar 18, 7:10 am, "@matheuseduardo" <matheuseduardo....@gmail.com>
wrote:
> welcome to "401 Not Authorized", seems to be the same error I'm 
> receiving<https://groups.google.com/d/msg/twitter-development-talk/lKb4w_N9sN0/...>
> .
> I'm still looking for solution.

-- 
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