News for hackers. Stuff that matters.
Re:Yes, browsers do cache SSL resources, so please use Googl... by briansmith on Wednesday January 19, 2011 @05:54PM (#2121631)
If this caching allows a website to switch from using HTTP to HTTPS within its budget, then I think the net effect is very positive. We can't have bad website administrators/developers holding back real security improvements with their incompetence. Really, caching is a very small security impact compared to other problems that such an administrator is likely to cause.
Re:Yes, browsers do cache SSL resources, so please use Googl... by amalcon on Wednesday January 19, 2011 @06:22PM (#2121732)
Again, absolutely right. Remember, though, that we're not talking about the capability here: we're talking about the default. A (well-run) website can get all the caching benefits by including a HTTP header. The article is about a well-run website that does exactly this. The default only matters at all for poorly-run websites.

Given that poorly run websites are considerably less likely to be worried about scaling issues, the caching is mostly inconsequential. So, would we prefer to give the poorly-run website a mostly inconsequential security benefit or a mostly inconsequential scaling benefit?

Re:Yes, browsers do cache SSL resources, so please use Googl... by andybak on Thursday January 20, 2011 @05:22AM (#2123215)
We probably want to remove any excuse for not switching to https. Perceived performance penalties, inconsequential or not, might hold back many sites.