| CARVIEW |
Every repository with this icon (
) is private.
Every repository with this icon (
) is public.
| Description: | A python library for the Twitter API. OAuth, python 3, complete coverage, streaming API edit |
-
0 votes
0 comments Created about 23 hours ago by joshthecoderoauth api.twitter.com causing 404'sBugxIssue reported on twitter-dev mailing list by Josh Bleecher Snyder. Copy of email follows:
Hi all,
The tweepy twitter client uses api.twitter.com for the host for oauth calls:
REQUEST_TOKEN_URL = 'https://api.twitter.com/oauth/request_token' AUTHORIZATION_URL = 'https://api.twitter.com/oauth/authorize' AUTHENTICATE_URL = 'https://api.twitter.com/oauth/authenticate' ACCESS_TOKEN_URL = 'https://api.twitter.com/oauth/access_token'
I've found that this works, until the user tries to sign out or sign
up during the authorization; if this happens, they get a 404. If,
however, twitter.com is used as the host:REQUEST_TOKEN_URL = 'https://twitter.com/oauth/request_token' AUTHORIZATION_URL = 'https://twitter.com/oauth/authorize' AUTHENTICATE_URL = 'https://twitter.com/oauth/authenticate' ACCESS_TOKEN_URL = 'https://twitter.com/oauth/access_token'
then everything, including signout and signup, works. This also
matches the instructions at
https://twitter.com/oauth_clients/details/%d.>However, it strikes me as odd that the oauth stuff half works at
api.twitter.com.My question is: What is the bug? That the api.twitter.com oauth
endpoints only partially work -- in which case tweepy is fine and I
should file a bug with Twitter -- OR that the api.twitter.com oauth
works at all -- in which case I should ping the author of tweepy and
perhaps suggest to Twitter that they remove this partial functionality
to prevent future confusion?Many thanks,
Josh-----End of email------
Comments
