3 ms·
From an idealistic point of view you're right, but in practice I disagree as HTTPS doesn't have persistent cache. So even without the encryption overhead, HTTPS
by laumars 13y ago
From an idealistic point of view you're right, but in practice I disagree as HTTPS doesn't have persistent cache. So even without the encryption overhead, HTTPS can be very costly for popular sites if they don't have user logins (eg news sites).
- tlogan 13y agoI still have to build company where I see problem where HTTP makes things faster than HTTPS. When I come to level that HTTPS is causing too much CPU usage I will be super super happy.
- joevandyk 13y agoit's not the cpu usage people worry about generally, it's the extra network trips / latency.
- riquito 13y agoSPDY requires encryption and yet it's overall faster than HTTP. If you have HTTPS on you may as well serve your pages over SPDY to the browsers that support it
- laumars 13y agoSPDY is less secure than HTTPS though[1]. Plus also supported by less web browsers / HTTP clients than HTTPS too. [1] http://www.pcworld.com/article/262307/crime_attack_abuses_ssltls_data_compression_feature_to_hijack_https_sessions.html http://www.pcworld.com/article/262307/crime_attack_abuses_ss...
- riquito 13y agoDid you even read the article you linked? The CRIME attack involves SSL/TLS, that both HTTPS and SPDY use.
- laumars 13y agoThe CRIME attack isn't just blindly attacking SSL/TLS like you rudely insinuated. CRIME specifically targets traffic over compressed SSL/TLS connections, using the deflation to leak cookies. The simple fix to this is to disable SSL/TLS compression, which is easily done in HTTPS (and in fact should be disabled if you want PCI compliance), but SSL/TLS compression cannot be disabled in SPDY. Sorry I didn't categorically spell this out for you earlier, I forgot some people need spoon-feeding the facts about the technology they advocate - even after you've already cited a massively dumbed down article on the subject already. (and nasty tone of my post is a result of me getting fed up with the way how you, and everyone else it seems, feels is appropriate to talk to each other on HN. This place never used to be quite so rude)
- riquito 13y agoI'm sorry, I was certainly rude, please excuse me.
- agwa 13y ago> HTTPS doesn't have persistent cache This is untrue so please don't perpetuate this myth. If you send the `Cache-Control: public` header, the resource will be cached to disk just as it would without HTTPS.
- laumars 13y ago> This is untrue so please don't perpetuate this myth. That sentence is somewhat unnecessary as I wouldn't have posted that unless I believed it to be true. The rest of your post is valid enough (in fact extremely helpful) not to need to such a prefix. Anyhow, I'm not out to start an argument and I genuinely am grateful you have corrected me because obviously I wasn't aware of the "public" option in the cache-control header and this is something I can actually put to use right away. So thank you for the correction :)
- ars_technician 13y agoIt may have been a little harsh, but I think it was necessary to point out that it wasn't true and that he wasn't just posting some hack or workaround.
- agwa 13y ago> not to need to such a prefix You're right; sorry about that. I do get annoyed when I see bogus reasons for not deploying HTTPS. It's made all the worse by people who actually know better but spread FUD because they stand to make a profit from selling expensive HTTPS accelerator appliances. But that's clearly not the case here and doesn't excuse my comment, which, upon reflection, was too harsh.
- laumars 13y agoThat's ok. As you said, I should know better (and now I do)