No HTTP/2

Hey Appleman1234, you are running nginx/1.10.3, but you don't even bother to add keyword "http2" to enable HTTP2? There's a real improvement over certain network conditions. Find lines like these in your nginx configuration: listen 107.161.19.243:443 ssl; listen [2604:180:1:c59::2c97]:443 ssl; Please change them to: listen 107.161.19.243:443 ssl http2; listen [2604:180:1:c59::2c97]:443 ssl http2; Thank you very much.

>>2118 On mobile and old machines (mostly the 5 of us who still use old pentium 4's), http/2 adds considerable client cpu overhead in my experience. Moreso than pipelining paired with encryption ever did. I am yet to find a reasonable explanation why, it just does. I have no opposition to it although I would be affected, it is just something to be aware of.

>>2120 Oh, never heard of this issue before. Never thought it can use that much of resources. Maybe deploying ChaCha20-Poly1305 can significantly improve performance for machines without hardware AES. But as we know Appleman1234 is not a fan of backups fancy server configuration anyway. Isn't there a way to switch off HTTP/2 manually? In FireFox it is called network.http.spdy.enabled.http2.

>>2118 You are mistaken, the site already supports HTTP2 and has the configuration you are mentioning in nginx. As per openssl s_client -connect lainchan.org:443 -nextprotoneg '' | grep Protocols 123629423056528:error:140920E3:SSL routines:ssl3_get_server_hello:parse tlsext:s3_clnt.c:1152: Protocols advertised by server: h2, http/1.1 What I think you are asking for is ALPN support so that Chrome uses HTTP2, which I am just making the relevant changes for now.

>>2118 >>2123 Is working currently! (Pale Meem Git ~27.3.0a1) >>2120 Ayy, sounds like a bummer. If the issue can't be resolved, then this sounds like the situation for locally disabing HTTP2 (and making sure the server continues to leave HTTP1.1 available!)