This section should contain various configuration examples for HTTP/2 (h2, h2c, etc..) plus common pitfalls (for example not setting a strong TLS cipher suite with h2).
Notice: This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our mailing lists.
You can override an earlier defined SetHandler
@@ -4472,10 +4472,14 @@ certain events before failing a request
The TimeOut directive defines the length
of time Apache httpd will wait for I/O in various circumstances:
-
-
When reading data from the client, the length of time to
+
+
When reading data from the client, the length of time to
wait for a TCP packet to arrive if the read buffer is
- empty.
+ empty.
+
For initial data on a new connection, this directive doesn't
+ take effect until after any configured
+ AcceptFilter has passed the new connection to the server.
+
When writing data to the client, the length of time to wait
for an acknowledgement of a packet if the send buffer is
@@ -4490,7 +4494,7 @@ certain events before failing a request
This module requires the service of mod_proxy. It provides the features used for
+ proxying HTTP/2 requests. mod_proxy_http2
+ supports HTTP/2 only. It does not
+ provide any downgrades to HTTP/1.1.
+
+
Thus, in order to get the ability of handling HTTP/2 proxy requests,
+ mod_proxy and mod_proxy_http2
+ have to be present in the server.
+
+
mod_proxy_http2 works with incoming requests
+ over HTTP/1.1 and HTTP/2 requests. If mod_proxy_http2
+ handles the frontend connection, requests against the same HTTP/2
+ backend are sent over a single connection, whenever possible.
+
+
This module relies on libnghttp2
+ to provide the core http/2 engine.
+
+
Warning
+
This module is experimental. Its behaviors, directives, and
+ defaults are subject to more change from release to
+ release relative to other standard modules. Users are encouraged to
+ consult the "CHANGES" file for potential updates.
+
+
+
Warning
+
Do not enable proxying until you have secured your server. Open proxy
+ servers are dangerous both to your network and to the Internet at
+ large.
Notice: This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our mailing lists.