From: Christophe Jaillet Date: Sun, 24 Jun 2018 19:19:11 +0000 (+0000) Subject: xforms X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9d8eaaaadce84c6737ed13e21c7b2b2791e2e7a1;p=apache xforms git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1834260 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/howto/http2.html.en b/docs/manual/howto/http2.html.en index d9f0a3cb42..b9a628fcac 100644 --- a/docs/manual/howto/http2.html.en +++ b/docs/manual/howto/http2.html.en @@ -42,7 +42,7 @@
  • Useful tools to debug HTTP/2
  • Server Push
  • Early Hints
    • -

    See also

    +

    See also

    top

    The HTTP/2 protocol

    @@ -74,7 +74,7 @@

    HTTP/2 in Apache httpd

    The HTTP/2 protocol is implemented by its own httpd module, aptly named - mod_http2. It implements the complete set + mod_http2. It implements the complete set of features described by RFC 7540 and supports HTTP/2 over cleartext (http:), as well as secure (https:) connections. The cleartext variant is named 'h2c', the secure one 'h2'. For h2c it allows the direct @@ -86,8 +86,8 @@

    Build httpd with HTTP/2 support

    -

    mod_http2 uses the library of nghttp2 - as its implementation base. In order to build mod_http2 you need at least version 1.2.1 of +

    mod_http2 uses the library of nghttp2 + as its implementation base. In order to build mod_http2 you need at least version 1.2.1 of libnghttp2 installed on your system.

    When you ./configure you Apache httpd source tree, you need to give it '--enable-http2' as additional argument to trigger the build of the module. @@ -96,7 +96,7 @@ to configure.

    While that should do the trick for most, they are people who might prefer a statically linked nghttp2 in this module. For those, the option --enable-nghttp2-staticlib-deps - exists. It works quite similar to how one statically links openssl to mod_ssl.

    + exists. It works quite similar to how one statically links openssl to mod_ssl.

    Speaking of SSL, you need to be aware that most browsers will speak HTTP/2 only on https: URLs, so you need a server with SSL support. But not only that, you will need a SSL library that supports the ALPN extension. If OpenSSL is the library you use, you need @@ -106,7 +106,7 @@

    Basic Configuration

    -

    When you have a httpd built with mod_http2 you need some +

    When you have a httpd built with mod_http2 you need some basic configuration for it becoming active. The first thing, as with every Apache module, is that you need to load it:

    LoadModule http2_module modules/mod_http2.so
    @@ -131,7 +131,13 @@

    This allows only HTTP/1 on connections, except SSL connections to test.example.org which offer HTTP/2.

    Choose a strong SSLCipherSuite

    -

    The SSLCipherSuite needs to be configured with a strong TLS cipher suite. The current version of mod_http2 does not enforce any cipher but most clients do so. Pointing a browser to a h2 enabled server with a inappropriate cipher suite will force it to simply refuse and fall back to HTTP 1.1. This is a common mistake that is done while configuring httpd for HTTP/2 the first time, so please keep it in mind to avoid long debugging sessions! If you want to be sure about the cipher suite to choose please avoid the ones listed in the HTTP/2 TLS blacklist.

    +

    The SSLCipherSuite needs to be configured with + a strong TLS cipher suite. The current version of mod_http2 does not enforce any cipher but most + clients do so. Pointing a browser to a h2 enabled server with a inappropriate + cipher suite will force it to simply refuse and fall back to HTTP 1.1. This is a common mistake + that is done while configuring httpd for HTTP/2 the first time, so please keep it in mind to avoid + long debugging sessions! If you want to be sure about the cipher suite to choose please avoid + the ones listed in the HTTP/2 TLS blacklist.

    The order of protocols mentioned is also relevant. By default, the first one is the most preferred protocol. When a client offers multiple choices, the one most to the @@ -153,7 +159,8 @@ ordering will decide.

    A last thing: the protocols you configure are not checked for correctness or spelling. You can mention protocols that do not exist, so there is no need - to guard Protocols with any IfModule checks.

    + to guard Protocols with any + <IfModule> checks.

    For more advanced tips on configuration, see the modules section about dimensioning and how to manage multiple hosts with the same certificate.

    @@ -163,17 +170,17 @@

    HTTP/2 is supported in all multi-processing modules that come with httpd. However, if - you use the prefork mpm, there will be severe restrictions.

    -

    In prefork mod_http2 will only process one request at at time + you use the prefork mpm, there will be severe restrictions.

    +

    In prefork, mod_http2 will only process one request at at time per connection. But clients, such as browsers, will send many requests at the same time. If one of these takes long to process (or is a long polling one), the other requests will stall.

    -

    mod_http2 will not work around this limit by default. The reason is that - prefork is today only chosen, if you run processing engines that re not +

    mod_http2 will not work around this limit by default. The reason is that + prefork is today only chosen, if you run processing engines that are not prepared for multi-threading, e.g. will crash with more than one request.

    -

    If your setup can handle it, configuring event mpm is nowadays +

    If your setup can handle it, configuring event mpm is nowadays the best one (if supported on your platform).

    -

    If you are really stuck with prefork and want multiple requests, +

    If you are really stuck with prefork and want multiple requests, you can tweak the H2MinWorkers to make that possible. If it breaks, however, you own both parts.

    top
    @@ -211,7 +218,10 @@
  • h2load - useful to stress-test your server.

    • Chrome offers detailed HTTP/2 logs on its connections via the - special net-internals page. There is also an interesting extension for Chrome and Firefox to visualize when your browser is using HTTP/2.

    + special net-internals page. There is also an + interesting extension for Chrome + and Firefox + to visualize when your browser is using HTTP/2.

    top

    Server Push

    @@ -232,7 +242,7 @@

    To summarize: there is no one good strategy on how to make best use of this feature of HTTP/2 and everyone is still experimenting. So, how do you experiment with it in Apache httpd?

    -

    mod_http2 inspect response header for Link headers +

    mod_http2 inspect response header for Link headers in a certain format:

    Link </xxx.css>;rel=preload, </xxx.js>; rel=preload
    @@ -258,7 +268,7 @@

    There are people thinking about how a client can tell a server what it already has, so PUSHes for those things can be avoided, but this is all highly experimental right now.

    -

    Another experimental draft that has been implemented in mod_http2 +

    Another experimental draft that has been implemented in mod_http2 is the Accept-Push-Policy Header Field where a client can, for each request, define what kind of PUSHes it accepts.

    @@ -290,7 +300,7 @@ 
    H2EarlyHints on

    (It is not enabled by default since some older browser tripped on such responses.)

    -

    If this feature is on, you can the directive H2PushResource to +

    If this feature is on, you can the directive H2PushResource to trigger early hints and resource PUSHes:

    <Location /xxx.html>
     H2PushResource /xxx.css
@@ -301,8 +311,8 @@
     as the server starts processing the request. This may be much early than
     the time the first response headers have been determined, depending on your web
     application.
    
-    
    If H2Push is enabled, this will also start the PUSH right after the
-    103 response. If H2Push is disabled however, the 103 response will be send
+    
    If H2Push is enabled, this will also start the PUSH right after the
+    103 response. If H2Push is disabled however, the 103 response will be send
     nevertheless to the client.
    diff --git a/docs/manual/howto/http2.xml.es b/docs/manual/howto/http2.xml.es index fa765c3474..e6b93252fb 100644 --- a/docs/manual/howto/http2.xml.es +++ b/docs/manual/howto/http2.xml.es @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/howto/http2.xml.fr b/docs/manual/howto/http2.xml.fr index 401287c302..e035c688d9 100644 --- a/docs/manual/howto/http2.xml.fr +++ b/docs/manual/howto/http2.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/howto/http2.xml.meta b/docs/manual/howto/http2.xml.meta index cd0a8de064..9b93a6fba0 100644 --- a/docs/manual/howto/http2.xml.meta +++ b/docs/manual/howto/http2.xml.meta @@ -9,6 +9,6 @@ en es - fr + fr