From ff9469c6a2bdc148c4228623f1a35e56242a38dc Mon Sep 17 00:00:00 2001
From: Jim Jagielski Apache HTTP Server can be configured in both a forward and
reverse proxy (also known as gateway) mode.AJP13 (Apache JServe Protocol version
1.3)
+ SSL)CONNECT (for
- SSL) FastCGI ftp
+ HTTP/1.1HTTP/0.9, HTTP/1.0, and
- HTTP/1.1 SCGI
Under some circumstances, the server must spool request bodies - to disk to satisfy the requested handling of request bodies. For + to disk to satisfy the requested handling of request bodies. For example, this spooling will occur if the original body was sent with chunked encoding (and is large), but the administrator has asked for backend requests to be sent with Content-Length or as HTTP/1.0. @@ -414,7 +414,7 @@
X-Forwarded-For
X-Forwarded-Host
Host
+ Host
HTTP request header.X-Forwarded-Server
The
This option should normally be turned Off
. It is mostly
+
This option should normally be turned Off
. It is mostly
useful in special configurations like proxied mass name-based virtual
hosting, where the original Host header needs to be evaluated by the
backend server.
One additional parameter is available only to
The balancerurl is only needed when not in <Proxy balancer://...>
container directive. It corresponds to the url of a balancer defined in
If the first argument ends with a trailing /, the second argument should also end with a trailing / and vice @@ -845,7 +845,7 @@ expressions backend server's keep-alive timeout.
The pool of connections is maintained per web server child
- process, and max
and other settings are not coordinated
+ process, and max
and other settings are not coordinated
among all child processes, except when only one child process is allowed
by configuration or MPM design.
On
.
+ set this property value to On
.
KEEP_ALIVE
messages on inactive connections and thus prevent the firewall to drop the connection.
To enable keepalive set this property value to On
.
- The frequency of initial and subsequent TCP keepalive probes +
The frequency of initial and subsequent TCP keepalive probes depends on global OS settings, and may be as high as 2 hours. To be useful, - the frequency configured in the OS must be smaller than the threshold used + the frequency configured in the OS must be smaller than the threshold used by the firewall.
D: Worker is disabled and will not accept any requests. |
S: Worker is administratively stopped. |
I: Worker is in ignore-errors mode, and will always be considered available. |
H: Worker is in hot-standby mode and will only be used if no other + viable workers are available. |
E: Worker is in an error state. |
N: Worker is in drain mode, and will only accept existing sticky sessions + destined for itself and ignore all other requests. |
If the Proxy directive scheme starts with the
- balancer://
(eg: balancer://cluster/
,
+ balancer://
(eg: balancer://cluster/
,
any path information is ignored) then a virtual worker that does not really
communicate with the backend server will be created. Instead it is responsible
for the management of several "real" workers. In that case the special set of
@@ -1036,12 +1045,12 @@ expressions
byrequests
, to perform weighted
request counting, bytraffic
, to perform weighted
- traffic byte count balancing, or bybusyness
, to perform
+ traffic byte count balancing, or bybusyness
, to perform
pending request balancing. Default is byrequests
.
A sample balancer setup
This directive is not supported in
In almost every case there's no reason to change that value.
If used with AJP this directive sets the maximum AJP packet size in
- bytes. If you change it from the default, you must also change the
+ bytes. If you change it from the default, you must also change the
packetSize
attribute of your AJP connector on the
Tomcat side! The attribute packetSize
is only available
in Tomcat 5.5.20+
and 6.0.2+
Normally it is not necessary to change the maximum packet size. Problems with the default value have been reported when sending certificates or certificate chains.
- +Domain name comparisons are done without regard to the case, and
Domains are always assumed to be anchored in the root of the
@@ -1530,7 +1539,7 @@ directly
An IPAddr does not need to be resolved by the DNS system, so
it can result in more effective apache performance. This directive is useful for reverse-proxy setups, where you want to
- have a common look and feel on the error pages seen by the end user.
+ This directive is useful for reverse-proxy setups, where you want to
+ have a common look and feel on the error pages seen by the end user.
This also allows for included files (via