Restricting api.twitter.com to SSL/TLS traffic

Jan 6, 2014 at 6:25 PM
What is the impact of this modification for the application using linqtotwitter ?

https://dev.twitter.com/discussions/24239
Coordinator
Jan 6, 2014 at 7:58 PM
Hi,

By default, there isn't an impact. The Twitter API is only on v1.1 now. When LINQ to Twitter upgraded to support v1.1, all of the default URLs were set to https.

Now, there is a chance for someone to shoot themselves in the foot because TwitterContext and IOAuthAuthorizers/IAuthorizers expose base URL properties that the user can change. This proved to be helpful in scenarios where Twitter offered a beta API and URLs changed. However, it also opens the possibility that someone, for some reason, might have been setting these properties manually and used an unsecure protocol (http). In those cases (where the user manually configured http), Twitter will begin returning errors on Jan 14th. There's also a failure scenario for Mono users that might not have configured certificates to work with Twitter and may have opted to manually configure URLs as http as a (unsecure) work-around. In those cases, their code will start receiving errors from Twitter API too.

Just to restate, all versions of LINQ to Twitter v2.1.0 and above use SSL by default. If you want to test, follow @TwitterAPI and learn when their blackout tests will start on Jan 7th.

@JoeMayo
Jan 7, 2014 at 11:59 AM
Thanks Joe!