Full Speed Ahead with HTTP/2 on Google Cloud Platform

googlecloudplatform.blogspot.com

64 points·waffle_ss··10 comments

Isn't one of the big performance advantages of HTTP2 multiplexing/Server Push? It'd be nice if they spent some time talking about how to take advantage of those improvements on their platform.

Inside my request handler, I ought to be able to say "If you're on HTTP2, push out these files:" and have AppEngine behave accordingly.

multiplexing should be automatic, but prioritization and push are different, obviously. Ilya Grigorik just tweeted[1] this project[2] for server push on app engine.

[1] https://twitter.com/igrigorik/status/652267370241654784

[2] https://github.com/GoogleChrome/http2push-gae

Yep! One thing to note, the header is likely to change at some point from X-Associated-Content to the emerging link preload standard (in-progress spec: https://w3c.github.io/preload/ )

still no support on cloudfront or elb on aws

It's a poor workaround, but you can set your ELBs in TCP mode, and terminate TLS and HTTP/2 on the instances directly.

Of course; Amazon prefers launching dozens of new products every year to fixing or improving their existing services.

Challenge for anyone supporting SPDY today (which has a lot more users) is HTTP/2 and SPDY are somewhat incompatible, so you have to choose.

Isn't SPDY deprecated for HTTP/2 though?

Yes. Even if they support SPDY it will be quite useful - http://caniuse.com/#search=spdy

Support for HTTP2 is catching up pretty quickly though, just lacking some love in the default android browser.

http://caniuse.com/#search=http2 63%

http://caniuse.com/#search=spdy 79%

Reply on news.ycombinator.com