News for hackers. Stuff that matters.
Re:The state and rate of HTTP/2 adoption by bhouston on Tuesday March 31, 2015 @08:14AM (#9295641)
I think the floodgates will open once there is a http2 module for nginx. We are still on spdy/3 because of this.

Details: http://nginx.com/blog/how-nginx-plans-to-support-http2/

I think it would be amazing for the CDNs, especially Amazon, to support HTTP2. But I've heard mostly silence from Amazon -- Cloudfront doesn't even support SPDY, which I though would have been useful already at this point.

Re:The state and rate of HTTP/2 adoption by jgrahamc on Tuesday March 31, 2015 @08:26AM (#9295694)
From CloudFlare's perspective we currently support SPDY for all customers and will support HTTP/2 once NGINX with it becomes available.

We are committed to support for new protocols for all customers. We've rolled out SPDY, IPv6, HSTS, HTTPS (free certs) for all and are close to adding DNSSEC and will add HTTP/2. We're not waiting for these things to gain traction.

To give you an idea of what we are doing and the impact take a look at this chart of SPDY deployment.

http://w3techs.com/technologies/details/ce-spdy/all/all

There's a sudden increase in sites (a doubling) using SPDY. That's when CloudFlare have every single customer free HTTPS and SPDY.

Re:The state and rate of HTTP/2 adoption by spb on Tuesday March 31, 2015 @04:24PM (#9299632)
What about content push? Will CloudFlare only do passthrough of pushes from HTTP/2 servers, will it support extended HTTP/1.1 headers as described in https://news.ycombinator.com/item?id=9296526, or will it add content pushes based on parsing the HTML if optimizations are turned on?
Re:The state and rate of HTTP/2 adoption by bagder on Tuesday March 31, 2015 @09:15AM (#9295882)
That's excellent to hear, thanks! If you have a public URL with such a statement I'd link to it from the post... (hint hint) =)
Re:The state and rate of HTTP/2 adoption by jgrahamc on Tuesday March 31, 2015 @09:26AM (#9295957)
I'm CloudFlare's "CTO". Link to that comment above.
Re:The state and rate of HTTP/2 adoption by e911 on Tuesday March 31, 2015 @01:51PM (#9298439)
Will WebSockets also be supported for all customers?
Re:The state and rate of HTTP/2 adoption by jgrahamc on Tuesday March 31, 2015 @01:58PM (#9298500)
Stay tuned.
Re:The state and rate of HTTP/2 adoption by billyhoffman on Tuesday March 31, 2015 @11:31AM (#9296975)
> But I've heard mostly silence from Amazon

Interestingly Amazon was one of the first non-Google companies to use SPDY. The Silk browser, first shipped in fall of 2011, includes an "acceleration feature." With it Amazon proxies your traffic and does a bunch of one the fly front-end optimizations (gzipping everything, lossless image optimization, giant shared caching proxy, basically a subset what mod_pagespeed can do). SPDY (and now presumably HTTP/2) is used between the tablet and Amazon's data centers.

Re:The state and rate of HTTP/2 adoption by thom_nic on Tuesday March 31, 2015 @01:22PM (#9298146)
I've been watching this open feature request[0] to add SPDY support for AWS ELB. Been open since 2012 and hasn't seen any real response from Amazon. Very disappointing. ELB is pretty much a given for any publicly-facing web service running on AWS.

[0] https://forums.aws.amazon.com/thread.jspa?threadID=90109

Re:The state and rate of HTTP/2 adoption by billyhoffman on Tuesday March 31, 2015 @01:57PM (#9298493)
Now that is strange, since Amazon specifically touted that Silk was being powered by EC2 instances. Almost certainly they are using a load balancer. Perhaps they rolled their own.
Re:The state and rate of HTTP/2 adoption by jimktrains2 on Tuesday March 31, 2015 @09:29AM (#9295972)
How would a CDN take advantage of the features of HTTP? Will they be able to use server-push? or will using HTTP2 just create more overhead because clients will connect, upgrade, request, get file, close. rinse-wash-repeat?
Re:The state and rate of HTTP/2 adoption by jgrahamc on Tuesday March 31, 2015 @10:19AM (#9296325)
I can only speak for CloudFlare, but we are planning to look into how to use Server Push to help our clients. Since we'll have assets in cache we can push them to clients quickly and it'll be a question of deciding/predicting what to push and when.
Re:The state and rate of HTTP/2 adoption by Alex3917 on Tuesday March 31, 2015 @09:33AM (#9296002)
> I think it would be amazing for the CDNs, especially Amazon, to support HTTP2.

The problem is that HTTP2 is basically a competitor, since one of the big value propositions of Cloudfront is that they fix a lot of the broken parts of HTTP. E.g. they achieve big performance improvements by keeping open persistent connections between the CDN and the webserver, which is an issue that HTTP2 ameliorates with multiplexing (since you no longer need a new connection for each static asset).

Re:The state and rate of HTTP/2 adoption by billyhoffman on Tuesday March 31, 2015 @11:39AM (#9297058)
The valuable proposition of a CDN is to improve load times by decreasing latency via geographically distributed servers. HTTP2 doesn't diminish this value.

CloudFront's extra features like keeping the open persistent connection is used for faster requests to the origin and faster edge server cache invalidation. HTTP2's multiplexing would actually help a CDN, since it decreases the load and number of incoming requests for static assets to the edge servers. CDN's are largely paid by bandwidth, and the edges are going to be delivering the same about of content regardless of whether it is transmitted using HTTP1 or HTTP2 (minus a tiny about due to the response header compression feature of HTTP2). So using HTTP2 will reduce there costs while allowing them to charge the same amount (or more make more money if the CDN offers it as an "accelerator service").

In short, HTTP2 is not a competitor to CDN's, even CDN's with fancy "extra" features, because the primary value prop of a CDN is decreasing latency.

Re:The state and rate of HTTP/2 adoption by Alex3917 on Tuesday March 31, 2015 @12:20PM (#9297506)
Obviously you'll still want to use a CDN even with HTTP2 for the reasons you mention. However, with HTTP2 I see Cloudfront as being less differentiated from any other CDN.
Re:The state and rate of HTTP/2 adoption by bhouston on Tuesday March 31, 2015 @10:16AM (#9296306)
> one of the big value propositions of Cloudfront is that they fix a lot of the broken parts of HTTP

Sort of, but we have slow delivery times of our static assets to non-North American locations (round-trip time), thus a CDN with local nodes helps here.

It also reduces the load on our servers, allowing us to focus on serving dynamic content fast, without having to optimize serving static stuff repeatedly -- as we serve a ton of static content and it can hog our bandwidth out of our boxes.

Re:The state and rate of HTTP/2 adoption by vbtechguy on Wednesday April 01, 2015 @03:33AM (#9302153)
Indeed I am waiting on Nginx HTTP/2 support too. Already testing OpenLiteSpeed and h2o HTTP/2 support at https://h2ohttp2.centminmod.com/webpagetests1.html.
Re:The state and rate of HTTP/2 adoption by MichaelGG on Tuesday March 31, 2015 @02:41PM (#9298877)
It'd also be nice if Microsoft shipped an easy-to-install plugin for IIS. I know, I know, they have this ... design ... where that handling is done by HTTP.SYS in the kernel. But their technical decisions like that shouldn't impact how they deliver updates.
Re:The state and rate of HTTP/2 adoption by mikecousins on Tuesday March 31, 2015 @06:24PM (#9300319)
And hopefully they land it on Azure quickly as well.
Re:The state and rate of HTTP/2 adoption by latro12 on Tuesday March 31, 2015 @09:33AM (#9296005)
Also, having a larger base of users that have browsers that support HTTP2 will make it a higher priority for devs to modify their servers to utilize HTTP2.