From: Luca Toscano Date: Thu, 25 Feb 2016 08:49:02 +0000 (+0000) Subject: Proposal for a new summary of mod_http2's doc X-Git-Tag: 2.5.0-alpha~2017 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e82af17d5b315f1a698adc5e576ed6ebdfa41b48;p=apache Proposal for a new summary of mod_http2's doc git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1732262 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_http2.xml b/docs/manual/mod/mod_http2.xml index 8f8b0a0273..53ec68c5cf 100644 --- a/docs/manual/mod/mod_http2.xml +++ b/docs/manual/mod/mod_http2.xml @@ -43,15 +43,24 @@ consult the "CHANGES" file for potential updates.

-

You must enable HTTP/2 via Protocols in order to use the - functionality described in this document:

+

You must enable HTTP/2 via Protocols in order to use the + functionality described in this document. The HTTP/2 protocol does not require the use of encryption so two schemes are available: h2 (HTTP/2 over TLS) and h2c (HTTP/2 over TCP).

+ +

Two useful configuration schemes are:

+ HTTP/2 in a VirtualHost context (TLS only) - Protocols h2 http/1.1 +Protocols h2 http/1.1 +

Allows HTTP/2 negotiation (h2) via TLS ALPN in a secure VirtualHost. HTTP/2 preamble checking (Direct mode, see H2Direct) is disabled by default for h2.

+
-

h2 (HTTP/2 over TLS) is the preferred connection scheme chosen by browsers up to now, but the HTTP/2 protocol does not require the use of encryption. To enable h2c (HTTP/2 over TCP) please check the H2Direct directive first.

+ HTTP/2 in a Server context (TLS and cleartext) + +Protocols h2 h2c http/1.1 + +

Allows HTTP/2 negotiation (h2) via TLS ALPN for secure VirtualHost. Allows HTTP/2 cleartext negotiation (h2c) upgrading from an initial HTTP/1.1 connection or via HTTP/2 preamble checking (Direct mode, see H2Direct).

+

Refer to the official HTTP/2 FAQ for any doubt about the protocol.