Twitter's SSL/TLS Requirement Breaks Authorization URL

[ericsund]

As of today (January 14, 2014), Twitter announced that connections to their API will have to go through TLS/SSL connections.

https://dev.twitter.com/discussions/24239

Is may be what is partially or fully responsible for the 403 Forbidden error Tweepy raises when attempting to get the authorization URL. I've ran my program on more than one computer, and this issue is new.

Traceback (most recent call last):
File "Wolf's Den.py", line 42, in
auth_url = auth.get_authorization_url()
File "/usr/lib/python2.7/site-packages/tweepy-2.1-py2.7.egg/tweepy/auth.py", line 96, in get_authorization_url
raise TweepError(e)
tweepy.error.TweepError: HTTP Error 403: Forbidden

If this is not the reason, does anyone have an idea what might be causing a 403? What I do find interesting is my app still functions by manually obtaining the access token/secret from dev.twitter.com. This might mean it's simply a problem with Tweepy, then.

Source: http://www.github.com/Altazon97/WolfsDen/
Tweepy 2.1 (01/14/2014)

[yosida95]

This problem is occurred because tweepy is using HTTP in default. Your application can authorization by passing one argument to constructor of tweepy.auth.OAuthHandler, secure=True.

auth = tweepy.auth.OAuthHandler(CONSUMER_KEY, CONSUMER_SECRET, secure=True)

[ericsund]

Yes, that does work. That change ported the traffic through a secure connection which makes it comply with the change. Thanks @yosida95!

[tzermias]

Thanks @yosida95!
Although it works fine for tweepy API calls, when I use Streaming API (StreamListener) this still returns me 401 errors. Any ideas?

[yosida95]

@tzermias This issue may help you: https://dev.twitter.com/discussions/2941

[tzermias]

@yosida95 It worked! The issue was that the computer clock was 10 minutes ahead! When I corrected it, the Streaming API worked just fine! Thanks again!