Monday, April 4, 2011

[twitter-dev] Re: 401 unauthorized

The https to http hack worked for me consistently for a while but now
even this no longer works for my app. Can anyone else confirm this?

On Mar 30, 8:10 am, Nick Spacek <nick.spa...@gmail.com> wrote:
> > Sorry, what hack is that?  I've heard a bunch of advice on working
> > around this, but nothing conclusive.
>
> I believe he means changing fromhttps://api.twitter.comtohttp://api.twitter.com. I can confirm that this works for me as well.
> Obviously not ideal, but an interim 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

No comments:

Post a Comment