From: Joe Orton
Date: Tue, 4 Jan 2022 08:39:41 +0000 (+0000)
Subject: Transforms. [skip ci]
X-Git-Tag: 2.5.0-alpha2-ci-test-only~601
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=09d5430a67df39f253ba6ea4e05cbb87f470e631;p=thirdparty%2Fapache%2Fhttpd.git
Transforms. [skip ci]
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1896665 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/mod/core.html.en.utf8 b/docs/manual/mod/core.html.en.utf8
index 48a96d8cd56..b935709cc28 100644
--- a/docs/manual/mod/core.html.en.utf8
+++ b/docs/manual/mod/core.html.en.utf8
@@ -852,11 +852,6 @@ which no other media type configuration could be found.
send the response without a Content-Type header field and the
recipient may attempt to guess the media type.
-See also
-
@@ -899,6 +894,11 @@ DocumentRoot "/var/www/${servername}/htdocs"
directives, beyond any enclosing virtual host.
+See also
+
@@ -1932,12 +1932,12 @@ to the network
This directive allows to configure the maximum number of pipelined
responses, which remain pending so long as pipelined request are received.
- When the limit is reached, reponses are forcibly flushed to the network in
+ When the limit is reached, responses are forcibly flushed to the network in
blocking mode, until passing under the limit again.
FlushMaxPipelined
helps constraining memory
- usage. When set to 0 pipelining is disabled, when set to
- -1 there is no limit (FlushMaxThreshold
+ usage. When set to 0
pipelining is disabled, when set to
+ -1
there is no limit (FlushMaxThreshold
still applies).
@@ -1946,7 +1946,7 @@ to the network
Description: | Threshold above which pending data are flushed to the
network |
-Syntax: | FlushMaxThresholdnumber-of-bytes |
+Syntax: | FlushMaxThreshold number-of-bytes |
Default: | FlushMaxThreshold 65536 |
Context: | server config, virtual host |
Status: | Core |
@@ -1958,7 +1958,7 @@ network
the network in blocking mode, until passing under the limit again.
FlushMaxThreshold
helps constraining memory
- usage. When set to 0 or a too small value there are actually
+ usage. When set to 0
or a too small value there are actually
no pending data, but for threaded MPMs there can be more threads busy
waiting for the network thus less ones available to handle the other
simultaneous connections.
diff --git a/docs/manual/mod/core.xml.de b/docs/manual/mod/core.xml.de
index d79b4334279..1290747375d 100644
--- a/docs/manual/mod/core.xml.de
+++ b/docs/manual/mod/core.xml.de
@@ -1,7 +1,7 @@
-
+
+
+
diff --git a/docs/manual/mod/core.xml.ja b/docs/manual/mod/core.xml.ja
index 90c0e3bd2f8..8239a96c033 100644
--- a/docs/manual/mod/core.xml.ja
+++ b/docs/manual/mod/core.xml.ja
@@ -1,7 +1,7 @@
-
+
+
+
-
+