Twitter to set all users to HTTPS by default

Twitter has announced that each one user sessions would be set to HTTPS by default.

The social networking site initially introduced an HTTPS option last March via a user setting, instead of via a specific website. By August 2011, Twitter began switching user sessions to HTTPS by default for some users.

In a blog post, Twitter said: “Last year, we added the option to always use HTTPS when accessing Twitter.com on the net. This setting makes your Twitter experience safer by protecting your information, and it's especially helpful when you use Twitter over an unsecured internet connection like a public WiFi network.

“Now, HTTPS would be on by default for all users, when you check in. While you prefer to not use it, you may turn it off on your Account Settings page. HTTPS is among the best ways to keep your account safe and it'll only recover as we continue to enhance HTTPS support on our web and mobile clients.”

Graham Cluley, senior technology consultant at Sophos, said: “Twitter wins the award for grooviest website of the day, due to the great move they have got announced if you want to help protect the privacy of millions of users.

“But what concerning the other big social networks? With Google Plus, things are simple. It has always had HTTPS turned on. Nice one. With Facebook, however, it is a different story. Although the social networking giant gave users the choice to enable HTTPS/SSL a year ago, it's still disabled by default and, even if enabled, only claims it is going to be used ‘when possible'.”

Last month, Twitter acquired anti-malware firm Dasient, with the seller saying it would bring its technology, tools and team to Twitter.

However, the HTTPS move could mean that Twitter may be blocked in Iran, as readwriteweb.com reported over the weekend that the Iranian government is obstructing access to websites that use HTTPS, meaning that sites equivalent to Google, Gmail, Yahoo! and online banking portals can be inaccessible.