QUOTE(aloc1234 @ Mar 2 2013, 17:27)

What's the downside of using https? I mean, if there were only advantages it would simply be the default protocol everywhere, right?
Signed SSL certificates aren't free and are provided on a per-domain/subdomain basis.
That's $50+ per year per domain. One for the main site, the forums, galleries, etc.
Since information is encrypted, it consumes more server resources to perform the encryption. Noticeable for a high-traffic site.
More importantly, if a page is encrypted, some browsers expect the assets (images, CSS, JS) to be provided via SSL as well.
This can cause issues (especially with the galleries and H@H), but a simple workaround is to only force SSL on certain parts of the site.
Basically: (HTTP) main page -> (HTTPS) login page -> (HTTP) rest of the site
There's also the issue of having your certificates expire and service disruptions. This recently happened to [
blogs.msdn.com]
Windows Azure.
tl;dr: too much work