5 ms·
Using nghttp2 to work around Nginx HTTP/2 bugs
- blfr 10y agoSpecifically, the "stable" version of nginx Is there any reason not to use mainline? This is what nginx recommend, it's not a -dev at all. I haven't been bitten yet anyway. http://nginx.org/en/linux_packages.html http://nginx.org/en/linux_packages.html
- Rafert 10y agoExactly, nginx stable is more like a LTS branch. See https://www.nginx.com/blog/nginx-1-6-1-7-released/ https://www.nginx.com/blog/nginx-1-6-1-7-released/ which also mentions "Note that stable does not mean more reliable or more bug-free. In fact, the mainline is generally regarded as more reliable because we port all bug fixes to it, and not just critical fixes as for the stable branch. [..] We recommend that in general you deploy the NGINX mainline branch at all times."
- secure 10y agonghttpx could be used to support server push (see https://nghttp2.org/documentation/nghttpx.1.html#server-push https://nghttp2.org/documentation/nghttpx.1.html#server-push), which nginx does not currently support (see https://stackoverflow.com/questions/33537199/does-the-nginx-http-2-module-support-server-push https://stackoverflow.com/questions/33537199/does-the-nginx-...) — neat!
- therealmarv 10y agoI've read that Cloudflare open sourced their nginx http/2+spdy implementation for nginx https://blog.cloudflare.com/open-sourcing-our-nginx-http-2-spdy-code/ https://blog.cloudflare.com/open-sourcing-our-nginx-http-2-s... I would rather give Cloudflare's modified nginx a shot than not using nginx at all. https://github.com/cloudflare/sslconfig/pull/36 https://github.com/cloudflare/sslconfig/pull/36
- andrewguy9 10y agoWhy not just turn off http2 support in config until stable has good support?
- omginternets 10y agoExactly what I was wondeirng. Can one really speak of a need for HTTP2 rather than a yearning desire, at most?
- coldtea 10y agoYes, anybody who runs a large site and gets far better performance out of it for the majority by now of clients who support it.
- omginternets 10y agoI'm replying to your post, specifically, but the other comments seem to be making the same point: HTTP2 confers a performance advantage. So I repeat my question: is this speed advantage stricto-sensu necessary? Why can't one "just" spin up a few more EC2 instances until this is fixed? Is there a case in which HTTP2 is necessary, and HTTP1 just won't cut it? I think that's the sense of the original question, and I think it's a valid question when talking about hacking one's way around bugs that are going to get fixed anyway. I'm open to being wrong about this, but I'm surprised at the resistance to this question.
- MichaelGG 10y agoThe perf advantage is in user loading times. HTTP1 won't cut it, and no amount of hardware on the server will, either. Just adding "SPDY" to nginx on some customer sites was enough to reduce load times by double digit %. (10-30 IIRC) I think SPDY might be a workaround for a bit; it's still supported this year right?
- coldtea 10y ago>I think SPDY might be a workaround for a bit; it's still supported this year right? No, Nginx dropped it (they only offer HTTP2 since 1.9.5) and Chrome dropped it from the client too this year IIRC.
- Svenskunganka 10y agoFor those of you that absolutely need strong HTTP/2 support, I highly recommend checking out H2O[0]. It has much less features than NGINX, but is very lightweight and has good performance with low resource footprint. [0]: https://h2o.examp1e.net/ https://h2o.examp1e.net/
- mozumder 10y agoI was looking at that. It doesn't seem to have WSGI support for Python apps, though.
- xorcist 10y ago.. or just good old Apache.
- Freaky 10y agomod_http2 is still considered experimental, and the source of 2 of the 3 vulnerabilities announced for 2.4 this year.
- aw3c2 10y agohttps://caddyserver.com/ https://caddyserver.com/ ! With Let's Encrypt built-in.
- therealmarv 10y agointeresting project. Never heard of it before.
- leesalminen 10y ago> Specifically, the "stable" version of nginx can't do HTTP/2 POST on any current browser without nginx dropping and resetting the connection. I hit this bug a while back. StackOverflow responders said I was crazy. I went to trac.nginx.org and while preparing a bug report, I saw that it had already been reported just a day prior. Felt good knowing I was not crazy, and there was a bug in nginx.
- breakingcups 10y agoWait, so the advice to fix my end-all-be-all HTTP proxy application is to run another proxy in front of it?