From 3f8a5522a9429326b550547f61b758c795c8b905 Mon Sep 17 00:00:00 2001 From: Christophe Jaillet Date: Sun, 26 Dec 2021 10:36:17 +0000 Subject: Fix a typo. Prefer to when giving the value of a parameter Add a missing space Add a missing link [skip ci] git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1896413 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/manual') diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml index 2798615146..d637d9d896 100644 --- a/docs/manual/mod/core.xml +++ b/docs/manual/mod/core.xml @@ -2042,12 +2042,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).

@@ -2056,7 +2056,7 @@ to the network FlushMaxThreshold Threshold above which pending data are flushed to the network -FlushMaxThresholdnumber-of-bytes +FlushMaxThreshold number-of-bytes FlushMaxThreshold 65536 server configvirtual host @@ -2068,7 +2068,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.

-- cgit v1.2.3