Configuring Apache

-Most of the directives are allowed once in the global part of the Apache httpd +Most of the directives are allowed once in the global part of the Apache HTTP Server configuration and once in every <VirtualHost> elements. Exceptions from this rule are explicitly listed in the table below.
@@ -42,15 +42,15 @@ Exceptions from this rule are again expl See especially JkMountCopy.
-Warning: If Apache httpd and Tomcat are configured to serve content from -the same filing system location then care must be taken to ensure that httpd is +Warning: If Apache and Tomcat are configured to serve content from +the same file system location then care must be taken to ensure that Apache is not able to serve inappropriate content such as the contents of the WEB-INF directory or JSP source code.
-This could occur if the httpd DocumentRoot +This could occur if the Apache DocumentRoot overlaps with a Tomcat Host's appBase or the docBase of any Context. It could -also occur when using the httpd Alias directive with a Tomcat Host's appBase or +also occur when using the Apache Alias directive with a Tomcat Host's appBase or the docBase of any Context.
@@ -71,7 +71,7 @@ value. Enables setting worker properties inside Apache configuration file. The syntax is the same as in the JkWorkersFile (usually workers.properties). Simply prefix each line with "JkWorkerProperty" to put it directly into -the Apache httpd config files. +the Apache config files.
This directive is allowed multiple times. It must be put into the global part of the configuration. @@ -95,7 +95,7 @@ drive and not an NFS share.
The shared memory contains configuration and runtime information for load balancer -workers and their members. It is need in order that all apache children +workers and their members. It is need in order that all Apache children
share the same status information for load balancing members (OK, ERROR, ...),
share the information about load taken by the individual workers,
@@ -290,7 +290,7 @@ to add SSLOptions +ExportCertData<

 
   Specifically, mod_jk will export the following environment variables from
-  Apache httpd to Tomcat under these request attributes as per the
+  Apache to Tomcat under these request attributes as per the
   Servlet Specification 3.0, section 3.8:
 
 
@@ -554,7 +554,7 @@ be used for piped logging:
 
 
 JkLogLevel
-set the log level between :
+set the log level between:
 

@@ -601,7 +601,7 @@ See above for details.
 
 
 You can log mod_jk information using the Apache standard module mod_log_config.
-The module sets several notes in the Apache httpd notes table.
+The module sets several notes in the Apache notes table.
 Most of them are are only useful in combination with a load balancer worker.
 
 
@@ -613,26 +613,26 @@ Most of them are are only useful in comb
                                                          Before version 1.2.26 only available if JkRequestLogFormat is set.
   Request duration in seconds and microseconds.

                                                          Before version 1.2.26 only available if JkRequestLogFormat is set.
-  Load-Balancer: Name of the first worker tried
-  Load-Balancer: Type of the first worker tried
-  Load-Balancer: Access count for the first worker tried
-  Load-Balancer: Count of created sessions for the first worker tried
-  Load-Balancer: Bytes read for the first worker tried
-  Load-Balancer: Bytes transferred for the first worker tried
-  Load-Balancer: Error count for the first worker tried
-  Load-Balancer: Busy count for the first worker tried
-  Load-Balancer: Activation state for the first worker tried
-  Load-Balancer: Error state for the first worker tried
-  Load-Balancer: Name of the last worker tried
-  Load-Balancer: Type of the last worker tried
-  Load-Balancer: Access count for the last worker tried
-  Load-Balancer: Count of created sessions for the last worker tried
-  Load-Balancer: Bytes read for the last worker tried
-  Load-Balancer: Bytes transferred for the last worker tried
-  Load-Balancer: Error count for the last worker tried
-  Load-Balancer: Busy count for the last worker tried
-  Load-Balancer: Activation state for the last worker tried
-  Load-Balancer: Error state for the last worker tried
+  Load balancer: Name of the first worker tried
+  Load balancer: Type of the first worker tried
+  Load balancer: Access count for the first worker tried
+  Load balancer: Count of created sessions for the first worker tried
+  Load balancer: Bytes read for the first worker tried
+  Load balancer: Bytes transferred for the first worker tried
+  Load balancer: Error count for the first worker tried
+  Load balancer: Busy count for the first worker tried
+  Load balancer: Activation state for the first worker tried
+  Load balancer: Error state for the first worker tried
+  Load balancer: Name of the last worker tried
+  Load balancer: Type of the last worker tried
+  Load balancer: Access count for the last worker tried
+  Load balancer: Count of created sessions for the last worker tried
+  Load balancer: Bytes read for the last worker tried
+  Load balancer: Bytes transferred for the last worker tried
+  Load balancer: Error count for the last worker tried
+  Load balancer: Busy count for the last worker tried
+  Load balancer: Activation state for the last worker tried
+  Load balancer: Error state for the last worker tried
 
 
 
@@ -717,7 +717,7 @@ options(vhost) = plus_options(global) -
 
 
 Using JkOptions ForwardURIProxy, the forwarded URI
-will be partially reencoded after processing inside Apache httpd and
+will be partially reencoded after processing inside Apache and
 before forwarding to Tomcat. This will be compatible with local
 URL manipulation by mod_rewrite and with URL encoded session ids.
 
@@ -746,7 +746,7 @@ will not work.
 
 

 Using JkOptions ForwardURICompat, the forwarded URI will
-be decoded by Apache httpd. Encoded characters will be decoded and
+be decoded by Apache. Encoded characters will be decoded and
 explicit path components like ".." will already be resolved.
 This is less spec compliant and is not safe if you are using
 prefix JkMount. This option will allow to rewrite URIs with
@@ -835,7 +835,7 @@ bypassing your unmount rules.
 
 

 JkOptions ForwardDirectories is used in conjunction with DirectoryIndex
-directive of Apache web server. As such mod_dir should be available to Apache,
+directive of Apache. As such mod_dir should be available to Apache,
 statically or dynamically (DSO)
 

 

@@ -876,9 +876,9 @@ file that Tomcat normally serves - for i
 
 

 Setting JkOptions ForwardLocalAddress, you ask mod_jk to send the local address,
-of the Apache web server instead remote client address. This can be used by
-Tomcat remote address valve for allowing connections only from registered Apache
-web servers.
+of the Apache HTTP Server instead remote client address. This can be used by the
+Tomcat remote address valve for allowing connections only from configured Apache
+servers.
 
   
   JkOptions     +ForwardLocalAddress
@@ -950,7 +950,7 @@ TCP keepalive value in your OS.
 
 
 
-JkOptions ForwardKeySize,  you ask mod_jk, when using ajp13, to forward also the SSL Key Size  as 
+JkOptions ForwardKeySize, you ask mod_jk, when using ajp13, to forward also the SSL Key Size  as 
 required by Servlet API 2.3.
 This flag shouldn't be set when servlet engine is Tomcat 3.2.x (on by default).
 
@@ -963,7 +963,7 @@ This flag shouldn't be set when servlet
 
 
 
-JkOptions ForwardSSLCertChain,  you ask mod_jk, when using ajp13,
+JkOptions ForwardSSLCertChain, you ask mod_jk, when using ajp13,
 to forward SSL certificate chain (off by default).
 Mod_jk only passes the SSL_CLIENT_CERT to the AJP connector. This is not a
 problem with self-signed certificates or certificates directly signed by the
@@ -1077,34 +1077,33 @@ More complex patterns in JkUnMount worke
 JkAutoAlias directive automatically Alias webapp context directories into
 the Apache document space. It enables Apache to serve a static context while Tomcat
 serving dynamic context. This directive is used for convenience so that you don't
-have to put an apache Alias directive for each application directory inside Tomcat's
+have to put an Apache Alias directive for each application directory inside Tomcat's
 webapp directory. For security reasons it is strongly recommended that JkMount
 is used to pass all requests to Tomcat by default and JkUnMount is used to
-explicitly exclude static content to be served by httpd. It should also be noted
-that content served by httpd will bypass any security constraints defined in the
+explicitly exclude static content to be served by Apache. It should also be noted
+that content served by Apache will bypass any security constraints defined in the
 application's web.xml.
 
 
   # enter the full path to the tomcat webapps directory
-  JkAutoAlias /opt/tomtact/webapps
+  JkAutoAlias /opt/tomcat/webapps
 
 The following example shows how to serve a dynamic context by
 Tomcat and static using Apache. The webapps directory has to
-be accessible by apache.
+be accessible by Apache.
 
 
   # enter the full path to the tomcat webapps directory
-  JkAutoAlias /opt/tomtact/webapps
+  JkAutoAlias /opt/tomcat/webapps
 
-  # Mount 'servlets-examples' directory. It's physical location
-  # is assumed to be in the /opt/tomtact/webapps/servlets-examples
+  # Mount 'examples' directory. It's physical location
+  # is assumed to be in the /opt/tomcat/webapps/examples
   # ajp13w is a worker defined in the workers.properties
-  JkMount /servlets-examples/* ajp13w
+  JkMount /examples/* ajp13w
 
-  # Unmount desired static content from servlets-examples webapp.
-  # This content will be served by the httpd directly.
-  JkUnMount /servlets-examples/*.gif ajp13w
-  JkUnMount /servlets-examples/*.jpg ajp13w
+  # Unmount desired static content from examples webapp.
+  # This content will be served by the Apache directly.
+  JkUnMount /*.gif ajp13w
 
 Note that you can have a single JkAutoAlias directive per virtual
 host inside your httpd.conf
@@ -1145,11 +1144,11 @@ An exclusion can be disabled by prefixin
 
   # Sample uriworkermap.properties file
 
-  /servlets-examples/*=ajp13w
-  # Do not map .jpeg files
-  !/servlets-examples/*.jpeg=ajp13w
+  /examples/*=ajp13w
+  # Do not map .gif files
+  !/*.gif=ajp13w
   # Make jsp examples initially disabled  
-  -/jsp-examples/*=ajp13w
+  -/examples/jsp/*=ajp13w
 
 
At run time you can change the content of this file. For example
 removing minus signs will enable the previously disabled uri mappings.

Modified: tomcat/jk/trunk/xdocs/reference/iis.xml
URL: http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/reference/iis.xml?rev=1700577&r1=1700576&r2=1700577&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/reference/iis.xml (original)
+++ tomcat/jk/trunk/xdocs/reference/iis.xml Tue Sep  1 14:32:31 2015
@@ -24,7 +24,7 @@
 
     
         Mladen Turk
-        Configuring IIS
+        Configuring the ISAPI redirector for Microsoft IIS
     
 
 
@@ -35,7 +35,7 @@ The Tomcat redirector requires three ent
 
 

 
-isapi_redirect.dll - The IIS server plugin, either obtain a pre-built DLL or build it yourself (see the build section).
+isapi_redirect.dll - The IIS ISAPI redirector plugin, either obtain a pre-built DLL or build it yourself (see the build section).
 
 
 workers.properties - A file that describes the host(s) and port(s) used by the workers (Tomcat processes). 
@@ -70,7 +70,7 @@ because the library is not loadable into
 
 
 
-ISAPI redirector reads configuration from the registry, create a new registry key named :
+ISAPI redirector reads configuration from the registry, create a new registry key named:
 
 
 "HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0"
@@ -94,7 +94,7 @@ A value pointing to location where log f
 
If one of the log rotation settings (log_rotationtime or log_filesize) are specified then the actual log file name is based on this setting.
 If the log file name includes any '%' characters, then it is treated as a format string for strftime(3), 
 e.g. c:\tomcat\logs\isapi-%Y-%m-%d-%H_%M_%S.log. Otherwise, the suffix .nnnnnnnnnn is automatically added and is the time in seconds.
-A full list of format string substitutions can be found in the Apache rotatelogs documentation
+A full list of format string substitutions can be found in the Apache rotatelogs documentation
 
 
 A string value for log level 
@@ -336,7 +336,7 @@ log_file=$(JKISAPI_PATH)\$(JKISAPI_NAME)
 

 
 The ISAPI redirector with version 1.2.31 can perform log rotation, with configuration and behaviour similar to the 
-rotatelogs program provided with Apache HTTP Server.
+rotatelogs program provided with Apache HTTP Server.
 
 
 To configure log rotation, configure a log_file, and one of the log_rotationtime or log_filesize options.
@@ -380,7 +380,7 @@ log_filesize=5M
 The log will be rotated whenever the configured limit is reached, but only if the log file name would change. If you configure
  a log file name with strftime(3) format codes in it, then ensure it specifies the same granularity
  as the rotation time configured, e.g. %Y-%m-%d if rotating daily (log_rotationtime=86400).
-
See the rotatelogs documentation for more examples.
+
See the rotatelogs documentation for more examples.
 
 
 
@@ -388,24 +388,24 @@ The log will be rotated whenever the con
 
 
 The ISAPI redirector with version 1.2.16 can do a simple URL rewriting. Although not
-as powerful as Apache Httpd's mod_rewrite, it allows a simple exchange of request URIs
+as powerful as Apache HTTP Server's mod_rewrite, it allows a simple exchange of request URIs
 
 
 The rule is in the form original-url-prefix=forward-url-prefix. For example:
 
 
-# Simple rewrite rules, making /jsp-examples
-# and /servlets-examples available under shorter URLs
-/jsp/=/jsp-examples/
-/servlets/=/servlets-examples/
+# Simple rewrite rules, making examples
+# available under shorter URLs
+/jsp/=/examples/jsp/
+/servlets/=/examples/servlets/
 
 
 You can also use regular expressions, if you prefix the rule with a tilde ~:
 
 
-# Complex rewrite rule, adding "-examples"
+# Complex rewrite rule, prefixing "/examples/"
 # to the first path component of all requests
-~/([^/]*)=/$1-examples
+~/([^/]*)=/examples/$1
 
 
 Note that uriworkermap.properties must use the URLs before rewriting.

Modified: tomcat/jk/trunk/xdocs/reference/status.xml
URL: http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/reference/status.xml?rev=1700577&r1=1700576&r2=1700577&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/reference/status.xml (original)
+++ tomcat/jk/trunk/xdocs/reference/status.xml Tue Sep  1 14:32:31 2015
@@ -175,7 +175,7 @@ The last three minimisation features hav
 Note: The following restriction has been removed starting with version 1.2.26.
 
 
-The Apache module mod_jk makes use of the internal Apache httpd infrastructure concerning
+The Apache module mod_jk makes use of the internal Apache HTTP Server infrastructure concerning
 virtual hosts. The downside of this is, that the status worker can only show URL maps, for
 the virtual host it is defined in. It is not able to reach the configuration objects
 for other virtual hosts. Of course you can define a status worker in any virtual host you
@@ -211,8 +211,8 @@ worker.mystatus.type=status
 Then we define a URL, which should be mapped to this worker, i.e. the URL we use
 to reach the functionality of the status worker. You can use any method mod_jk supports
 for the web server of your choice. Possibilities are maps inside uriworkermap.properties,
-an additional mount attribute in workers.properties, or in Apache JkMount. Here's an
-example for a uriworkermap.properties line:
+an additional mount attribute in workers.properties, or JkMount for the Apache HTTP Server.
+Here's an example for a uriworkermap.properties line:
 
 /private/admin/mystatus=mystatus
 

Modified: tomcat/jk/trunk/xdocs/reference/uriworkermap.xml
URL: http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/reference/uriworkermap.xml?rev=1700577&r1=1700576&r2=1700577&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/reference/uriworkermap.xml (original)
+++ tomcat/jk/trunk/xdocs/reference/uriworkermap.xml Tue Sep  1 14:32:31 2015
@@ -192,8 +192,8 @@ rules with equal numbers are sorted by t
 
 
 If both distinctions still do not suffice, then the defining source of the rule is considered.
-Rules defined in uriworkermap.properties come first, before rules defined by JkMount (Apache)
-and inside workers.properties using the mount attribute.
+Rules defined in uriworkermap.properties come first, before rules defined by JkMount
+(for the Apache HTTP Server) and inside workers.properties using the mount attribute.
 
 
 All disabled rules are ignored. Exclusion rules are applied after all normal rules
@@ -360,10 +360,11 @@ per mount. See their descriptions in the
 

 

 
-
+
 

 
-When using IIS you can restrict individual rules to special virtual hosts
+When using the ISAPI redirector for Microsoft IIS you can restrict
+individual rules to special virtual hosts
 by prefixing the URI pattern with the virtual host information.
 The rules is that the url must be prefixed with the host name.
 
@@ -388,10 +389,10 @@ the exclusion rule must be used
 
 
 
-
+
 

 
-For Apache you can define individual uriworkermap files per virtual host.
+For the Apache HTTP Server you can define individual uriworkermap files per virtual host.
 The directive JkMountFile can be used in the main server and in each virtual host.
 If a virtual host does not use JkMountfile, but JkMountCopy is set to 'On',
 then it inherits the JkMountFile from the main server. If you want all vhost to inherit
@@ -408,14 +409,14 @@ of the uriworkermap file. To keep the pe
 if the last check happened at least n seconds ago.
 
 
-For Apache you can configure the interval "n" using the directive JkMountFileReload,
-for IIS you would use the attribute worker_mount_reload.
+For the Apache HTTP Server you can configure the interval "n" using the directive JkMountFileReload,
+for Microsoft IIS you would use the attribute worker_mount_reload.
 The default value is 60 seconds. A value of "0" turns off the reloading.
 
 
 If the file changed, it gets reloaded completely. If there exist rules coming
 from other sources than the uriworkermap file (e.g. the workers.properties mount
-attribute or JkMount with Apache httpd), the new uriworkermap file gets dynamically
+attribute or JkMount for the Apache HTTP Server), the new uriworkermap file gets dynamically
 merged with these ones exactly like when you do a web server restart.
 
 
@@ -444,14 +445,14 @@ the type of the rule: Exact or Wildchar
 
 
 and the source of the rule definition: 'worker definition' for the workers.properties file (mount attribute),
-'JkMount' for Apache httpd JkMount and it's relatives and finally 'uriworkermap' for the uriworkermap file.
+'JkMount' for the Apache HTTP Server JkMount and it's relatives and finally 'uriworkermap' for the uriworkermap file.
 
 
 
 
 Note: The following restriction has been removed starting with version 1.2.26.
 

-For Apache httpd, there is an important subtlety: the request going to the status worker
+For the Apache HTTP Server, there is an important subtlety: the request going to the status worker
 gets executed in the context of some server (main or virtual). The status worker will only show the
 mapping rules, that are defined for this server (main or virtual).
 

@@ -465,7 +466,7 @@ the URI pattern
 
 

 and the source of the rule definition: 'worker definition' for the workers.properties file (mount attribute),
-'JkMount' for Apache httpd JkMount and it's relatives and finally 'uriworkermap' for the uriworkermap file.
+'JkMount' for the Apache HTTP Server JkMount and it's relatives and finally 'uriworkermap' for the uriworkermap file.
 
 


Modified: tomcat/jk/trunk/xdocs/reference/workers.xml
URL: http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/reference/workers.xml?rev=1700577&r1=1700576&r2=1700577&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/reference/workers.xml (original)
+++ tomcat/jk/trunk/xdocs/reference/workers.xml Tue Sep  1 14:32:31 2015
@@ -34,7 +34,7 @@
 
 A Tomcat worker is a Tomcat instance that is waiting to execute servlets or any other content
 on behalf of some web server. For example, we can have a web server such as
-Apache forwarding servlet requests to a Tomcat process (the worker) running behind it.
+the Apache HTTP Server forwarding servlet requests to a Tomcat process (the worker) running behind it.
 

 The scenario described above is a very simple one;
@@ -144,7 +144,7 @@ Each worker configuration directive cons
 
worker.<worker name>.<directive>=<value>

 The first word is always worker. 
-The second word is the worker name you can choose. In the case of load-balancing,
+The second word is the worker name you can choose. In the case of load balancing,
 the worker name has an additional meaning. Please consult the
 Load Balancer HowTo.
 
@@ -220,16 +220,19 @@ be unavailable or will misbehave. Those
 

 
-Type of the worker (can be one of ajp13, ajp14, jni, lb or status). The type of the worker
+Type of the worker (can be one of ajp12, ajp13, ajp14, jni, lb or status). The type of the worker
 defines the directives that can be applied to the worker.
 Type ajp13 is the preferred worker type that JK uses for communication
 between web server and Tomcat. This type of worker uses sockets as communication
-channel. For detailed description of the AJP13 protocol stack browse to
-AJPv13 protocol specification
+channel. For detailed description of the ajp13 protocol stack browse to
+AJPv13 protocol specification. Type lb is
+used for load balancing workers,
+type status for status workers.
 
-Type ajp14 is experimental and not recommended.
+
Type ajp14 is experimental and not recommended, type ajp12
+is obsolete.
 
-JNI workers have been deprecated. They will likely not work. Do not use them.
+JNI workers are no longer supported and will likely not work. Do not use them.
 
 
@@ -284,13 +287,13 @@ This feature has been added in jk 1.2
 
 
 
-This directive should be used when you have a firewall between your webserver
+This directive should be used when you have a firewall between your web server
 and the Tomcat engine, who tend to drop inactive connections. This flag will tell the Operating System
 to send KEEP_ALIVE messages on inactive connections (interval depend on global OS settings,
 generally 120 minutes), and thus prevent the firewall to cut inactive connections.
 To enable keepalive set this property value to true.
 
-The problem with Firewall cutting inactive connections is that sometimes, neither webserver or Tomcat
+The problem with Firewall cutting inactive connections is that sometimes, neither web server or Tomcat
 have information about the cut and couldn't handle it.
 
 
@@ -375,15 +378,16 @@ It will limit the number of those connec
 process can made.
 
 Connection pool size property is only used for multi threaded
-web servers such as Apache, IIS and Netscape/Sun. The connection_pool_size property
+web servers such as the Apache HTTP Server, Microsoft IIS and the iPlanet Web Server.
+The connection_pool_size property
 needs to reflect the number of requests one web server process should
 be able to send to a backend in parallel. Usually this is the same as
 the number of threads per web server process. JK will discover
-this number for the Apache web server automatically and set the pool size to
+this number for the Apache HTTP Server automatically and set the pool size to
 this value. For IIS the default value is 250 (before version 1.2.20: 10),
-for Netscape/Sun the default value is 1.
+for iPlanet the default value is 1.
 
-We strongly recommend adjusting this value for IIS and the Netscape/Sun
+
We strongly recommend adjusting this value for IIS and iPlanet
 to the number of requests one web server process should
 be able to send to a backend in parallel. You should measure how many connections
 you need during peak activity without performance problems, and then add some
@@ -391,7 +395,7 @@ percentage depending on your growth rate
 whether your web server processes are able to use at least as many threads,
 as you configured as the pool size.
 
-Do not use connection_pool_size with values higher then 1 on Apache 2.x prefork or Apache 1.3.x!
+Do not use connection_pool_size with values higher then 1 on Apache 2.x with prefork MPM or Apache 1.3.x!
 
 
 
@@ -399,7 +403,7 @@ Minimum size of the connection pool that
 
 Its default value is (connection_pool_size+1)/2.
 
-Do not use connection_pool_size with values higher then 1 on Apache 2.x prefork or Apache 1.3.x!
+Do not use connection_pool_minsize with values higher then 1 on Apache 2.x with prefork MPM or Apache 1.3.x!
 
 This feature has been added in jk 1.2.16.
 
@@ -415,7 +419,7 @@ a new ajp13 thread on Tomcat side.
 
 
 The problem is that after an ajp13 connection is created, the child won't drop it
-until killed. And since the webserver will keep its childs/threads running
+until killed. And since the web server will keep its childs/threads running
 to handle high-load, even it the child/thread handle only static contents, you could
 finish having many unused ajp13 threads on the Tomcat side.
 
@@ -440,7 +444,7 @@ This feature has been added in jk 1.2
 
 Only used for a member worker of a load balancer.
 
-The integer number lbfactor (load-balancing factor) is
+The integer number lbfactor (load balancing factor) is
 how much we expect this worker to work, or
 the worker's work quota. Load balancing factor is compared with other workers
 that makes the load balancer. For example if one worker has lb_factor 5 times higher then
@@ -472,21 +476,21 @@ Load balancer management includes:
 Instantiating the workers in the web server.
 
 

-Using the worker's load-balancing factor, perform weighed-round-robin load balancing where
+Using the worker's load balancing factor, perform weighted round-robin load balancing where
 high lbfactor means stronger machine (that is going to handle more requests)
 
 
 Keeping requests belonging to the same session executing on the same Tomcat worker.
 
 
-Identifying failed Tomcat workers, suspending requests to them and instead fall-backing on
+Identifying failed Tomcat workers, suspending requests to them and instead fail over on
 other workers managed by the lb worker.
 
 
 
 
-The overall result is that workers managed by the same lb worker are load-balanced
-(based on their lbfactor and current user session) and also fall-backed so a single
+The overall result is that workers managed by the same lb worker are load balanced
+(based on their lbfactor and current user session) and also fail over so a single
 Tomcat process death will not "kill" the entire site.
 
 
@@ -524,7 +528,7 @@ sticky_session is set to false. S
 is using a Session Manager which can persist session data across multiple
 instances of Tomcat.
 
-The sticky_session setting can be overwritten using the Apache httpd
+The sticky_session setting can be overwritten using the Apache HTTP Server
 environment variable JK_STICKY_IGNORE and the worker map extension for
 sticky_ignore. This has been added in version 1.2.33.
 
@@ -572,7 +576,7 @@ without a session cookie or URL encoding
 know, when a session is being invalidated, nor will it correct its load numbers
 according to session timeouts or worker failover. If you know request URLs, that will be
 called without a session ID but should not be counted as new sessions, you should
-add them to the stateless mapping rule extension or set the Apache HTTPD
+add them to the stateless mapping rule extension or set the Apache HTTP Server
 environment variable JK_STATELESS for them.
 
 
@@ -771,7 +775,7 @@ as a sub worker or member.
 
 
 
-Connect timeout property told webserver to send a PING request on ajp13 connection after
+Connect timeout property told web server to send a PING request on ajp13 connection after
 connection is established. The parameter is the delay in milliseconds to wait for the PONG reply.
 The default value zero disables the timeout (infinite timeout).
 
@@ -782,7 +786,7 @@ Disabled by default.
 
 
 
-Prepost timeout property told webserver to send a PING request on ajp13 connection before
+Prepost timeout property told web server to send a PING request on ajp13 connection before
 forwarding to it a request. The parameter is the delay in milliseconds to wait for the PONG reply.
 The default value zero disables the timeout (infinite timeout).
 

@@ -798,7 +802,7 @@ So this is not a timeout for the complet
 for the maximum time between two packets received from Tomcat. Usually the longest
 pause is between sending the request and getting the first packet of the response.
 

-If the timeout passes without any data received from Tomcat, the webserver will
+If the timeout passes without any data received from Tomcat, the web server will
 no longer wait for the rest of the response and send an error to the client (browser).
 Usually this does not mean, that the request is also aborted on the Tomcat backend.
 If the worker is a member of a load balancer, the load balancer might place the
@@ -806,11 +810,11 @@ worker into an error state and retry the
 See also max_reply_timeouts, retries and recovery_options.
 
 
-By default (value zero) the webserver will wait forever which could be an issue for you.
+By default (value zero) the web server will wait forever which could be an issue for you.
 If you set a reply_timeout, adjust it carefully if you have long running servlets.
 
 
-The reply_timeout can be overwritten using the Apache httpd environment variable
+The reply_timeout can be overwritten using the Apache HTTP Server environment variable
 JK_REPLY_TIMEOUT and the worker map extension for reply_timeout.
 
 
@@ -1163,13 +1167,13 @@ It will limit the number of those connec
 process can make.
 

 Cachesize property is used only for multi threaded 
-web servers such as Apache 2.0 (worker), IIS and Netscape. The cachesize property
+web servers such as Apache HTTP Server 2.x (all MPMs except prefork), IIS and iPlanet. The cachesize property
 should reflect the number of threads per child process. JK will discover
-the number of threads per child process on Apache 2 web server with worker-mpm and set
-its default value to match the ThreadsPerChild Apache directive. For IIS the default
-value is 10. For other web servers than Apache or IIS this value has to be set manually.
+the number of threads per child process on the Apache HTTP Server with threaded MPM and set
+its default value to match the current ThreadsPerChild Apache configuration. For IIS the default
+value is 10. For web servers other than Apache or IIS this value has to be set manually.
 
-Do not use cachesize with values higher then 1 on Apache 2.x prefork or Apache 1.3.x!
+Do not use cachesize with values higher then 1 on Apache 2.x with prefork MPM or Apache 1.3.x!
 
 
 
@@ -1183,7 +1187,7 @@ a new ajp13 thread on Tomcat side.
 
 
 The problem is that after an ajp13 connection is created, the child won't drop it
-until killed. And since the webserver will keep its childs/threads running
+until killed. And since the web server will keep its childs/threads running
 to handle high-load, even it the child/thread handle only static contents, you could
 finish having many unused ajp13 threads on the Tomcat side.
 
@@ -1191,7 +1195,7 @@ finish having many unused ajp13 threads
 
 
 This directive has been deprecated since 1.2.16.
-The number of seconds that told webserver to cut an ajp13 connection after some time of 
+The number of seconds that told web server to cut an ajp13 connection after some time of 
 inactivity. When choosing an endpoint for a request and the assigned socket is open, it will be
 closed if it was not used for the configured time.
 It's a good way to ensure that there won't too old threads living on Tomcat side, 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org