If you like this article or want to share your thoughts feel free to use the comment section down below or message and follow me on Twitter. And don’t forget to use HTTPS where ever you are! Hopefully this will help you bringing your web servers to HTTP/2. I’m still searching for a solution to fix that protocol advertisement issue.Ī correct check can be found at ConclusionĮnabling HTTP/2 on Debian stable using apache2 isn’t as simple as it should be.īy using the Debian testing package however it is possible in a secure and trusted way without much effort.
The problem is, that those tests only check the first request and all servers which doesn’t support NPN or ALPN will automatically fallback to HTTP/1.1 But it will add an upgrade header option so every further connect uses HTTP/2. If you check your server with HTTP2-Check you’ll still get the message: Now all your webpages should be HTTP/2 ready.Ĭheck it with your web browser using the developer tools. Now you can add Link-options to your HTTP header to push content to your clients. To improve the load speed of your pages the usage of H2Push is really useful. To use HTTP/2 the SSLCipherSuite is also important because HTTP/2 requires TLS1.2 in some browsers. Important here is the Protocols option which enables HTTP/2 in general. This creates the /etc/apache2/conf-available/nf file. Sudo a2enconf http2 & sudo apachectl -t & sudo systemctl reload apache2
SSLCipherSuite 'EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 EECDH EDH+aRSA !RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS' H2PushPriority application/javascript interleaved Sudo bash -c 'cat >/etc/apache2/conf-available/nf' << EOF
0 kommentar(er)
