5 ms·
From the comments on that article, it looks like Google will only implement SPDY for HTTPS, because Google believe that's the future of all HTTP requests. I'm
by grecy 15y ago
From the comments on that article, it looks like Google will only implement SPDY for HTTPS, because Google believe that's the future of all HTTP requests.
I'm not cool with that. I feel like a ton of HTTP requests are for very simple html pages that don't require any kind of login/security and the overhead of HTTPS is of no benefit.
- nickpresta 15y agoIf the page is just 'simple html', why does the overhead matter? I would imagine that the overhead of fetching data from a database, talking to the network, etc, would outweigh the cost of doing an SSL handshake if you bundle your resources correctly.
- ComputerGuru 15y agoYou're contradicting yourself here. If it's plain HTML, there's none of the database/intranet/etc going on and so every bit of overhead is noticeable... which is the point the GP was trying to make. Not that I share that opinion. I think the whole world needs to move on SSL, even though it's kinda broken in the current method where a select few companies make a crazy killing selling their SSL certs (although there are cheap alternatives).
- nickpresta 15y agoMy two points were unrelated. If it's a simple HTML site - who cares? A simple HTML site with < 100KB of content and < 15 resources to fetch isn't a bit deal anyways. Two or three seconds to a user on a mobile device isn't unreasonable. If the site is more complex, the SSL handshake most likely isn't your bottleneck. I found this[1] to be an interesting read. [1]: http://www.semicomplete.com/blog/geekery/ssl-latency.html http://www.semicomplete.com/blog/geekery/ssl-latency.html
- brandon 15y agoI'm completely cool with it. Modern equipment can handle plenty of SSL traffic, and SSL-by-default will protect me (and you) from lazy developers. The real question is whether or not this will proliferate and to what extent.
- zobzu 15y agoYeah but you've to pay for SSL certs that works in everyones browser without a fat "DONT GO TO THIS EVIL WEBSITE OMGOMG SELFSIGNED TERRORIST" Meaning you'd have to pay a tax to put your site on the net when everyone only uses SPDY.
- caf 15y agoYou haven't had to pay for SSL certs for several years now - for example http://www.startssl.com/ http://www.startssl.com/.
- wmf 15y agoThere's been some discussion that you could run SPDY with a self-signed cert and it just wouldn't show the lock. People need to make their opinions on this topic known to Google and Mozilla before the security model is finalized.
- ComputerGuru 15y agoDo you have any info on that? Links, references, mailing list messages, anything? That's super interesting and honestly, the way it should be. HTTPS w/out certificate verification is STILL more secure than HTTP and it should be treated as such - not as the black sheep that it currently is.
- wmf 15y agohttps://groups.google.com/forum/#!topic/spdy-dev/R3Pt4NE2bjc https://groups.google.com/forum/#!topic/spdy-dev/R3Pt4NE2bjc http://thread.gmane.org/gmane.ietf.http-wg/9960/focus=10001 http://thread.gmane.org/gmane.ietf.http-wg/9960/focus=10001 Like I said, they're just discussions and currently the tide is against us.
- modeless 15y agoPervasive end-to-end encryption is the only way to defeat deep packet inspection-based spying, throttling, and censorship, which is increasingly popular among governments and ISPs (and even end users e.g. Firesheep). The overhead of encryption is actually tiny, contrary to common perception. It should never be optional.
- sams99 15y agothat is not 100% true, you are always going to pay at least 1 extra round trip up front for an encrypted connection, for NY-Sydney latency this would wack on 250ms extra to the first request, http keep alive mitigates a bit.
- Daniel_Newby 15y agoEncrypted protocols can prearranged a session key and/or initialization vector to use for the next connection, dramatically reducing the start up delay.
- dr_rezzy 15y agoThis is my biggest concern. This means that whenever you want to run a simple HTTP server, you need a signed certificate. Well, thats a huge hassle. So its likely shortcuts will be adopted to make HTTPS adoption more practical for everyday usage. This could lead to the weakening of the entire trust based certificate system due to the demand/pressure of scale. Ok, so now you strengthen the trust system and inadvertently untrust large parts of the unregulated internet. Great, you have just implemented tiered internet. Those who qualify for the trust based system get rewarded with access to HTTP(S) 2.0, those who do not are condemned to HTTP 1.X. Congrats guys, great foresight.
- qznc 15y agoI don't think browsers will drop HTTP support in your lifetime. They still do FTP for example.