I'm currently in the process of making a site with 130,000 monthly visitors 100% SSL. https://www.londonfgss.com/thread32727.html https://www.londonfgss.com/th

I'm currently in the process of making a site with 130,000 monthly visitors 100% SSL. https://www.londonfgss.com/thread32727.html https://www.londonfgss.com/thread32727.html It's just a community forum, but things like ACTA and the erosion of privacy that our government is gradually executing all make me really question whether there are downsides. I'd originally made it available over SSL to help people access it from work without the proxies blocking it (works very well btw), but now it'll be everything. As part of this I'm doing a review of the styles, images, javascript, etc to ensure that I perform as few requests as possible due to the lack of caching. The software I'm using hasn't really considered requests. The view seems to have been "it's a one time hit and then it's cached", whereas in the SSL world you'll be good if you get a cached once-per-session model. It also complexifies things on the back-end, thinking of things like software load balancing and pass-through requests. All good stuff though, I get to learn about how to make this stuff work and scale at the same time as providing a great feature (privacy and security) to my users. Traditional models are worth breaking to gain these benefits.