5 ms·

what are the current http/2 server options?

by 0x006A 11y ago

vladaionescu 11y ago
As far as I understand, none for production use. I see that nginx implements SPDY (HTTP2 is based on SPDY), but not yet HTTP2. They promise to bring HTTP2 by end of year though - http://nginx.com/blog/how-nginx-plans-to-support-http2/ http://nginx.com/blog/how-nginx-plans-to-support-http2/ .
shurcooL 11y ago
Caddy looks like a good choice. https://caddyserver.com/ https://caddyserver.com/
tootie 11y ago
Undertow and Jetty are both Java options that support HTTP/2. I've been playing with both and it's still very rough around the edges (have to mess with bootpath to get ALPN to work), but it does work. F5 are supporting it now too.
- pimlottc 11y ago
  From the presentation, Jetty's smart push feature sounds really cool, do you know if there's more information available on that feature?
  - tootie 11y ago
    Basically it caches requests per referrer so the next time a request is made, it can guess what subsequent requests will be made. Documentation is still sparse and a lot of it is carryover from their SPDY features.
ropiku 11y ago
You can also use an http/2 reverse proxy in front like nghttp2 or H2O. https://nghttp2.org/ https://nghttp2.org/ https://h2o.examp1e.net/ https://h2o.examp1e.net/
olalonde 11y ago
There's a list of implementations here: https://github.com/http2/http2-spec/wiki/Implementations https://github.com/http2/http2-spec/wiki/Implementations
- oinksoft 11y ago
  According to the presentation, 9% of all HTTP on FF36 (for those who didn't disable this data collection) is HTTP/2. Surely there are people here using HTTP/2 in production: How are you serving HTTP/2 traffic? The listing itself is somewhat muddled ... "Twitter" is an entry, linking to the Twitter homepage, presumably that's responsible for most of this traffic? I found https://github.com/twitter/netty-http2 https://github.com/twitter/netty-http2 and https://github.com/twitter/hpack https://github.com/twitter/hpack on Twitter's GitHub.

what are the current http/2 server options?

by 0x006A 11y ago

what are the current http/2 server options?

As far as I understand, none for production use. I see that nginx implements SPDY (HTTP2 is based on SPDY), but not yet HTTP2. They promise to bring HTTP2 by end of year though - http://nginx.com/blog/how-nginx-plans-to-support-http2/ http://nginx.com/blog/how-nginx-plans-to-support-http2/ .

shurcooL 11y ago

Caddy looks like a good choice. https://caddyserver.com/ https://caddyserver.com/

tootie 11y ago

Undertow and Jetty are both Java options that support HTTP/2. I've been playing with both and it's still very rough around the edges (have to mess with bootpath to get ALPN to work), but it does work. F5 are supporting it now too.

pimlottc 11y ago
From the presentation, Jetty's smart push feature sounds really cool, do you know if there's more information available on that feature?
- tootie 11y ago
  Basically it caches requests per referrer so the next time a request is made, it can guess what subsequent requests will be made. Documentation is still sparse and a lot of it is carryover from their SPDY features.

ropiku 11y ago

You can also use an http/2 reverse proxy in front like nghttp2 or H2O. https://nghttp2.org/ https://nghttp2.org/ https://h2o.examp1e.net/ https://h2o.examp1e.net/

olalonde 11y ago

There's a list of implementations here: https://github.com/http2/http2-spec/wiki/Implementations https://github.com/http2/http2-spec/wiki/Implementations

oinksoft 11y ago
According to the presentation, 9% of all HTTP on FF36 (for those who didn't disable this data collection) is HTTP/2. Surely there are people here using HTTP/2 in production: How are you serving HTTP/2 traffic? The listing itself is somewhat muddled ... "Twitter" is an entry, linking to the Twitter homepage, presumably that's responsible for most of this traffic? I found https://github.com/twitter/netty-http2 https://github.com/twitter/netty-http2 and https://github.com/twitter/hpack https://github.com/twitter/hpack on Twitter's GitHub.