Author: kkolinko
Date: Thu Nov 10 04:11:35 2011
New Revision: 1200130
URL: http://svn.apache.org/viewvc?rev=1200130&view=rev
Log:
Merging r1187809 - Trailing whitespace removal from /webapps
/webapps/docs, 5
Modified:
tomcat/tc7.0.x/trunk/webapps/docs/config/listeners.xml
tomcat/tc7.0.x/trunk/webapps/docs/config/manager.xml
tomcat/tc7.0.x/trunk/webapps/docs/config/project.xml
tomcat/tc7.0.x/trunk/webapps/docs/config/realm.xml
tomcat/tc7.0.x/trunk/webapps/docs/config/resources.xml
tomcat/tc7.0.x/trunk/webapps/docs/config/server.xml
tomcat/tc7.0.x/trunk/webapps/docs/config/systemprops.xml
tomcat/tc7.0.x/trunk/webapps/docs/config/valve.xml
Modified: tomcat/tc7.0.x/trunk/webapps/docs/config/listeners.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/config/listeners.xml?rev=1200130&r1=1200129&r2=1200130&view=diff
==============================================================================
--- tomcat/tc7.0.x/trunk/webapps/docs/config/listeners.xml (original)
+++ tomcat/tc7.0.x/trunk/webapps/docs/config/listeners.xml Thu Nov 10 04:11:35
2011
@@ -38,7 +38,7 @@
actions when specific events occur, usually Tomcat starting or Tomcat
stopping.</p>
- <p>Listeners may be nested inside a <a href="server.html">Server</a>,
+ <p>Listeners may be nested inside a <a href="server.html">Server</a>,
<a href="engine.html">Engine</a>, <a href="host.html">Host</a> or
<a href="context.html">Context</a>. Some Listeners are only intended to be
nested inside specific elements. These constraints are noted in the
@@ -156,7 +156,7 @@
this listener starts as Tomcat's common class loader is the context class
loader at that time. It also provides work-arounds for known issues that
can result in locked JAR files.</p>
-
+
<p>This listener must only be nested within <a
href="server.html">Server</a>
elements.</p>
@@ -182,12 +182,12 @@
</attribute>
<attribute name="classesToInitialize" required="false">
- <p>List of comma-separated fully qualified class names to load and
initialize
- during the startup of this Listener. This allows to pre-load classes
that are
- known to provoke classloader leaks if they are loaded during a request
- processing. Non-JRE classes may be referenced, like
+ <p>List of comma-separated fully qualified class names to load and
initialize
+ during the startup of this Listener. This allows to pre-load classes
that are
+ known to provoke classloader leaks if they are loaded during a request
+ processing. Non-JRE classes may be referenced, like
<code>oracle.jdbc.driver.OracleTimeoutThreadPerVM</code>.
- The default value is empty, but specific JRE classes are loaded by
other leak
+ The default value is empty, but specific JRE classes are loaded by
other leak
protection features managed by other attributes of this Listener.</p>
</attribute>
@@ -218,24 +218,24 @@
<attribute name="ldapPoolProtection" required="false">
<p>Enables protection so that the PoolCleaner thread started by
- <code>com.sun.jndi.ldap.LdapPoolManager</code> does not result in a
- memory leak. The thread is started the first time the
- <code>LdapPoolManager</code> class is used if the system property
+ <code>com.sun.jndi.ldap.LdapPoolManager</code> does not result in a
+ memory leak. The thread is started the first time the
+ <code>LdapPoolManager</code> class is used if the system property
<code>com.sun.jndi.ldap.connect.pool.timeout</code> is set to a value
- greater than 0. Without this protection, if a web application uses
this
- class the PoolCleaner thread will be configured with the thread's
- context class loader set to the web application class loader which in
- turn will trigger a memory leak on reload. Defaults to
+ greater than 0. Without this protection, if a web application uses this
+ class the PoolCleaner thread will be configured with the thread's
+ context class loader set to the web application class loader which in
+ turn will trigger a memory leak on reload. Defaults to
<code>true</code>.</p>
</attribute>
<attribute name="securityLoginConfigurationProtection" required="false">
<p>Enables protection so that usage of the
- <code>javax.security.auth.login.Configuration</code> class by a web
- application does not provoke a memory leak. The first access of this
- class will trigger the initializer that will retain a static reference
- to the context class loader. The protection loads the class with the
- system class loader to ensure that the static initializer is not
+ <code>javax.security.auth.login.Configuration</code> class by a web
+ application does not provoke a memory leak. The first access of this
+ class will trigger the initializer that will retain a static reference
+ to the context class loader. The protection loads the class with the
+ system class loader to ensure that the static initializer is not
triggered by a web application. Defaults to <code>true</code>.</p>
</attribute>
@@ -379,7 +379,7 @@
</attribute>
</attributes>
-
+
<h3>Using file-based Authentication and Authorisation</h3>
<p>If this listener was configured in server.xml as:
@@ -438,7 +438,7 @@
</source>
then we would need to provide LDAP credentials instead.
</p>
-
+
<p><strong>Note that the examples above do not use SSL. JMX access should
be considered equivalent to administrative access and secured accordingly.
</strong></p>
Modified: tomcat/tc7.0.x/trunk/webapps/docs/config/manager.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/config/manager.xml?rev=1200130&r1=1200129&r2=1200130&view=diff
==============================================================================
--- tomcat/tc7.0.x/trunk/webapps/docs/config/manager.xml (original)
+++ tomcat/tc7.0.x/trunk/webapps/docs/config/manager.xml Thu Nov 10 04:11:35
2011
@@ -85,14 +85,14 @@
</attribute>
<attribute name="maxInactiveInterval" required="false">
- <p>The initial maximum time interval, in seconds,
+ <p>The initial maximum time interval, in seconds,
between client requests before a session is invalidated. A negative
value
will result in sessions never timing out. If the attribute is not
provided,
a default of 60 seconds is used.</p>
-
- <p>This attribute provides the initial value whenever a
- new session is created, but the interval may be dynamically
- varied by a servlet via the
+
+ <p>This attribute provides the initial value whenever a
+ new session is created, but the interval may be dynamically
+ varied by a servlet via the
<code>setMaxInactiveInterval</code> method of the
<code>HttpSession</code> object.</p>
</attribute>
@@ -131,7 +131,7 @@
across application restarts, if possible. The default is
"SESSIONS.ser".<br />See
<a href="#Persistence_Across_Restarts">Persistence Across Restarts</a>
- for more information. This persistence may be
+ for more information. This persistence may be
disabled by setting this attribute to an empty string.</p>
</attribute>
@@ -179,7 +179,7 @@
<code>org.apache.catalina.STRICT_SERVLET_COMPLIANCE</code>
<a href="systemprops.html">system properties</a> to <code>true</code> for
the persistent manager to work correctly.</p>
-
+
<p>The persistent implementation of <strong>Manager</strong> is
<strong>org.apache.catalina.session.PersistentManager</strong>. In
addition to the usual operations of creating and deleting sessions, a
Modified: tomcat/tc7.0.x/trunk/webapps/docs/config/project.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/config/project.xml?rev=1200130&r1=1200129&r2=1200130&view=diff
==============================================================================
--- tomcat/tc7.0.x/trunk/webapps/docs/config/project.xml (original)
+++ tomcat/tc7.0.x/trunk/webapps/docs/config/project.xml Thu Nov 10 04:11:35
2011
@@ -24,7 +24,7 @@
The Apache Tomcat Servlet/JSP Container
</logo>
-
+
<body>
<menu name="Links">
@@ -59,7 +59,7 @@
<item name="JarScanner" href="jar-scanner.html"/>
<item name="Listeners" href="listeners.html"/>
<item name="Loader" href="loader.html"/>
- <item name="Manager" href="manager.html"/>
+ <item name="Manager" href="manager.html"/>
<item name="Realm" href="realm.html"/>
<item name="Resources" href="resources.html"/>
<item name="Valve" href="valve.html"/>
@@ -68,7 +68,7 @@
<menu name="Cluster Elements">
<item name="Cluster" href="cluster.html"/>
<item name="Manager" href="cluster-manager.html"/>
- <item name="Channel" href="cluster-channel.html"/>
+ <item name="Channel" href="cluster-channel.html"/>
<item name="Channel/Membership" href="cluster-membership.html"/>
<item name="Channel/Sender" href="cluster-sender.html"/>
<item name="Channel/Receiver" href="cluster-receiver.html"/>
Modified: tomcat/tc7.0.x/trunk/webapps/docs/config/realm.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/config/realm.xml?rev=1200130&r1=1200129&r2=1200130&view=diff
==============================================================================
--- tomcat/tc7.0.x/trunk/webapps/docs/config/realm.xml (original)
+++ tomcat/tc7.0.x/trunk/webapps/docs/config/realm.xml Thu Nov 10 04:11:35 2011
@@ -50,8 +50,8 @@
containers, unless explicitly overridden.</p>
<p>For more in-depth information about container managed security in web
- applications, as well as more information on configuring and using the
- standard realm component implementations, please see the
+ applications, as well as more information on configuring and using the
+ standard realm component implementations, please see the
<a href="../realm-howto.html">Container-Managed Security Guide</a>.
</p>
@@ -140,7 +140,7 @@
to encode user passwords stored in the database. If not specified,
user passwords are assumed to be stored in clear-text.</p>
</attribute>
-
+
<attribute name="digestEncoding" required="false">
<p>The charset for encoding digests. If not specified, the platform
default will be used.</p>
@@ -245,12 +245,12 @@
</attribute>
<attribute name="localDataSource" required="false">
- <p>When the realm is nested inside a Context element, this allows the
+ <p>When the realm is nested inside a Context element, this allows the
realm to use a DataSource defined for the Context rather than a global
- DataSource. If not specified, the default is <code>false</code>: use
a
+ DataSource. If not specified, the default is <code>false</code>: use a
global DataSource.</p>
</attribute>
-
+
<attribute name="roleNameCol" required="true">
<p>Name of the column, in the "user roles" table, which contains
a role name assigned to the corresponding user.</p>
@@ -736,17 +736,17 @@
<attribute name="appName" required="true">
<p>The name of the application as configured in your login configuration
- file
+ file
(<a
href="http://download.oracle.com/javase/1.4.2/docs/guide/security/jaas/tutorials/LoginConfigFile.html";>JAAS
LoginConfig</a>).</p>
</attribute>
<attribute name="userClassNames" required="true">
- <p>A comma-separated list of the names of the classes that you have
made
+ <p>A comma-separated list of the names of the classes that you have
made
for your user <code>Principals</code>.</p>
</attribute>
<attribute name="roleClassNames" required="false">
- <p>A comma-separated list of the names of the classes that you have
made
+ <p>A comma-separated list of the names of the classes that you have
made
for your role <code>Principals</code>.</p>
</attribute>
@@ -801,10 +801,10 @@
<code>Realm</code> interface that extends the CombinedRealm to provide lock
out functionality to provide a user lock out mechanism if there are too
many
failed authentication attempts in a given period of time.</p>
-
+
<p>To ensure correct operation, there is a reasonable degree of
synchronization in this Realm.</p>
-
+
<p>This Realm does not require modification to the underlying Realms or the
associated user storage mechanisms. It achieves this by recording all
failed
logins, including those for users that do not exist. To prevent a DOS by
@@ -866,7 +866,7 @@
<strong><Realm></strong> elements may be nested inside it.</p>
<h3>Other Realm Implementations</h3>
-
+
<p>No other Realm implementation supports nested components.</p>
</section>
Modified: tomcat/tc7.0.x/trunk/webapps/docs/config/resources.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/config/resources.xml?rev=1200130&r1=1200129&r2=1200130&view=diff
==============================================================================
--- tomcat/tc7.0.x/trunk/webapps/docs/config/resources.xml (original)
+++ tomcat/tc7.0.x/trunk/webapps/docs/config/resources.xml Thu Nov 10 04:11:35
2011
@@ -36,7 +36,7 @@
<section name="Introduction">
<p>The <strong>Resources</strong> element represents the <em>web
- application static resources</em>, from which classes will be loaded,
+ application static resources</em>, from which classes will be loaded,
HTML, JSP and the other static files will be served. This allows the webapp
to reside on various mediums other than the filesystem, like compressed
in a WAR file, in a JDBC database, or in a more advanced versioning
@@ -48,14 +48,14 @@
access, access through the <code>ServletContext</code> interface, or native
access through the <code>DirectoryContext</code> interface.</p>
- <p><strong>Note: Running a webapp with non-filesystem based
- Resources implementations is only possible when the webapp does not
+ <p><strong>Note: Running a webapp with non-filesystem based
+ Resources implementations is only possible when the webapp does not
rely on direct filesystem access to its own resources, and uses the methods
in the ServletContext interface to access them.</strong></p>
- <p>A Resources element MAY be nested inside a
- <a href="context.html">Context</a> component. If it is not included,
- a default filesystem based Resources will be created automatically,
+ <p>A Resources element MAY be nested inside a
+ <a href="context.html">Context</a> component. If it is not included,
+ a default filesystem based Resources will be created automatically,
which is sufficient for most requirements.</p>
</section>
@@ -73,10 +73,10 @@
<attribute name="className" required="false">
<p>Java class name of the implementation to use. This class must
implement the <code>javax.naming.directory.DirContext</code> interface.
- It is recommended for optimal functionality and performance,
- but not mandatory, that the class extend
+ It is recommended for optimal functionality and performance,
+ but not mandatory, that the class extend
<code>org.apache.naming.resources.BaseDirContext</code>, as well as
- use the special object types provided in the
+ use the special object types provided in the
<code>org.apache.naming.resources</code> for returned objects.
If not specified, the standard value (defined below) will be used.</p>
</attribute>
@@ -89,7 +89,7 @@
<subsection name="Standard Implementation">
<p>The standard implementation of <strong>Resources</strong> is
- <strong>org.apache.naming.resources.FileDirContext</strong>, and
+ <strong>org.apache.naming.resources.FileDirContext</strong>, and
is configured by its parent Context element.</p>
</subsection>
Modified: tomcat/tc7.0.x/trunk/webapps/docs/config/server.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/config/server.xml?rev=1200130&r1=1200129&r2=1200130&view=diff
==============================================================================
--- tomcat/tc7.0.x/trunk/webapps/docs/config/server.xml (original)
+++ tomcat/tc7.0.x/trunk/webapps/docs/config/server.xml Thu Nov 10 04:11:35 2011
@@ -104,9 +104,9 @@
<p>The following components may be nested inside a <strong>Server</strong>
element:</p>
<ul>
- <li><a href="service.html"><strong>Service</strong></a> -
+ <li><a href="service.html"><strong>Service</strong></a> -
One or more service element.</li>
- <li><a
href="globalresources.html"><strong>GlobalNamingResources</strong></a> -
+ <li><a
href="globalresources.html"><strong>GlobalNamingResources</strong></a> -
Configure the JNDI global resources for the server.</li>
</ul>
Modified: tomcat/tc7.0.x/trunk/webapps/docs/config/systemprops.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/config/systemprops.xml?rev=1200130&r1=1200129&r2=1200130&view=diff
==============================================================================
--- tomcat/tc7.0.x/trunk/webapps/docs/config/systemprops.xml (original)
+++ tomcat/tc7.0.x/trunk/webapps/docs/config/systemprops.xml Thu Nov 10
04:11:35 2011
@@ -40,15 +40,15 @@
<section name="Property replacements">
<properties>
<property name="org.apache.tomcat.util.digester. PROPERTY_SOURCE">
- <p>Set this to a fully qualified name of a class that implements
+ <p>Set this to a fully qualified name of a class that implements
<code>org.apache.tomcat.util.IntrospectionUtils.PropertySource</code>.
Required to have a public constructor with no arguments.</p>
<p>Use this to add a property source, that will be invoked when
<code>${parameter}</code>
denoted parameters are found in the XML files that Tomcat parses.</p>
</property>
</properties>
-
-</section>
+
+</section>
<section name="Clustering">
<properties>
@@ -336,7 +336,7 @@
<code>true</code>, the default of this setting will be <code>true</code>,
else the default value will be <code>false</code>.</p>
</property>
-
+
<property
name="org.apache.tomcat.util.http. ServerCookie.ALLOW_EQUALS_IN_VALUE">
<p>If this is <code>true</code> Tomcat will allow '<code>=</code>'
@@ -406,12 +406,12 @@
<properties>
- <property name="org.apache.catalina.authenticator.
+ <property name="org.apache.catalina.authenticator.
Constants.SSO_SESSION_COOKIE_NAME">
<p>An alternative name for the single sign on session cookie. Defaults to
<code>JSESSIONIDSSO</code>.</p>
</property>
-
+
<property name="org.apache.catalina.core.
StandardHostValve.ACCESS_SESSION">
<p>If this is <code>true</code>, every request that is associated with a
session will cause the session's last accessed time to be updated
@@ -420,7 +420,7 @@
<code>true</code>, the default of this setting will be <code>true</code>,
else the default value will be <code>false</code>.</p>
</property>
-
+
<property
name="org.apache.catalina.session. StandardSession.ACTIVITY_CHECK">
<p>If this is <code>true</code>, Tomcat will track the number of active
@@ -454,9 +454,9 @@
<property name="org.apache.juli.formatter">
<p>If no logging configuration file is specified and no logging
configuration class is specified
using the <code>java.util.logging.config.class</code> and
<code>java.util.logging.config.file</code>
- properties the default logging framework <code>org.apache.juli</code>
will use the default
- <code>java.util.logging.SimpleFormatter</code> for all console
output.
- To simply override the console output formatter, one can use the
described property. Example:
+ properties the default logging framework <code>org.apache.juli</code>
will use the default
+ <code>java.util.logging.SimpleFormatter</code> for all console output.
+ To simply override the console output formatter, one can use the
described property. Example:
<code>-Dorg.apache.juli.formatter=org.apache.juli.OneLineFormatter</code></p>
</property>
<property name="org.apache.juli.AsyncOverflowDropType">
@@ -473,7 +473,7 @@
</property>
<property name="org.apache.juli.AsyncMaxRecordCount">
- <p>The max number of log records that the async logger will keep in
memory. When this limit is reached and a new record is being logged by the
+ <p>The max number of log records that the async logger will keep in
memory. When this limit is reached and a new record is being logged by the
JULI framework the system will take an action based on the
<code>org.apache.juli.AsyncOverflowDropType</code> setting.</p>
<p>The default value is <code>10000</code> records.
This number represents the global number of records, not on a per
handler basis.
@@ -571,13 +571,13 @@
<p>If <code>true</code>, use a shared selector for servlet
write/read.</p>
<p>If not specified, the default value of <code>true</code> will be
used.</p>
</property>
-
+
<property name="org.apache.catalina.startup. EXIT_ON_INIT_FAILURE">
<p>If <code>true</code>, the server will exit if an exception happens
during the server initialization phase.</p>
<p>If not specified, the default value of <code>false</code> will be
used.</p>
</property>
-
+
</properties>
Modified: tomcat/tc7.0.x/trunk/webapps/docs/config/valve.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/config/valve.xml?rev=1200130&r1=1200129&r2=1200130&view=diff
==============================================================================
--- tomcat/tc7.0.x/trunk/webapps/docs/config/valve.xml (original)
+++ tomcat/tc7.0.x/trunk/webapps/docs/config/valve.xml Thu Nov 10 04:11:35 2011
@@ -69,7 +69,7 @@
<p>Some requests may be handled by Tomcat before they are passed to a
container. These include redirects from /foo to /foo/ and the rejection of
invalid requests. Where Tomcat can identify the <code>Context</code> that
- would have handled the request, the request/response will be logged in the
+ would have handled the request, the request/response will be logged in the
<code>AccessLog</code>(s) associated <code>Context</code>,
<code>Host</code>
and <code>Engine</code>. Where Tomcat cannot identify the
<code>Context</code> that would have handled the request, e.g. in cases
@@ -141,7 +141,7 @@
attributes (typically set by the RemoteIpValve and similar) that should
be used to override the values returned by the request for remote
address, remote host, server port and protocol. If the attributes are
- not set, or this attribute is set to <code>false</code> then the
values
+ not set, or this attribute is set to <code>false</code> then the values
from the request will be used. If not set, the default value of
<code>false</code> will be used.</p>
</attribute>
@@ -208,7 +208,7 @@
<attribute name="buffered" required="false">
<p>Flag to determine if logging will be buffered.
- If set to <code>false</code>, then access logging will be written
after each
+ If set to <code>false</code>, then access logging will be written
after each
request. Default value: <code>true</code>
</p>
</attribute>
@@ -353,7 +353,7 @@
attributes (typically set by the RemoteIpValve and similar) that should
be used to override the values returned by the request for remote
address, remote host, server port and protocol. If the attributes are
- not set, or this attribute is set to <code>false</code> then the
values
+ not set, or this attribute is set to <code>false</code> then the values
from the request will be used. If not set, the default value of
<code>false</code> will be used.</p>
</attribute>
@@ -417,7 +417,7 @@
<attribute name="buffered" required="false">
<p>Flag to determine if logging will be buffered.
- If set to <code>false</code>, then access logging will be written
after each
+ If set to <code>false</code>, then access logging will be written
after each
request. Default value: <code>true</code>
</p>
</attribute>
@@ -650,19 +650,19 @@
</attribute>
<attribute name="requireReauthentication" required="false">
- <p>Default false. Flag to determine whether each request needs to be
+ <p>Default false. Flag to determine whether each request needs to be
reauthenticated to the security <strong>Realm</strong>. If "true", this
Valve uses cached security credentials (username and password) to
- reauthenticate to the <strong>Realm</strong> each request associated
- with an SSO session. If "false", the Valve can itself authenticate
- requests based on the presence of a valid SSO cookie, without
+ reauthenticate to the <strong>Realm</strong> each request associated
+ with an SSO session. If "false", the Valve can itself authenticate
+ requests based on the presence of a valid SSO cookie, without
rechecking with the <strong>Realm</strong>.</p>
</attribute>
-
+
<attribute name="cookieDomain" required="false">
<p>Sets the host domain to be used for sso cookies.</p>
</attribute>
-
+
</attributes>
</subsection>
@@ -944,7 +944,7 @@
from the request. If not set, the encoding of the request body will be
used.</p>
</attribute>
-
+
<attribute name="className" required="true">
<p>Java class name of the implementation to use. This MUST be set to
<strong>org.apache.catalina.authenticator.FormAuthenticator</strong>.</p>
@@ -959,7 +959,7 @@
workaround for browser caching issues. If not set, the default value of
<code>true</code> will be used.</p>
</attribute>
-
+
<attribute name="landingPage" required="false">
<p>Controls the behavior of the FORM authentication process if the
process is misused, for example by directly requesting the login page
@@ -1219,7 +1219,7 @@
<section name="Remote IP Valve">
<subsection name="Introduction">
-
+
<p>Tomcat port of
<a
href="http://httpd.apache.org/docs/trunk/mod/mod_remoteip.html";>mod_remoteip</a>,
this valve replaces the apparent client remote IP address and hostname for
@@ -1227,14 +1227,14 @@
via a request headers (e.g. "X-Forwarded-For").</p>
<p>Another feature of this valve is to replace the apparent scheme
- (http/https), server port and <code>request.secure</code> with the scheme
presented
- by a proxy or a load balancer via a request header
+ (http/https), server port and <code>request.secure</code> with the scheme
presented
+ by a proxy or a load balancer via a request header
(e.g. "X-Forwarded-Proto").</p>
-
+
<p>This Valve may be used at the <code>Engine</code>, <code>Host</code> or
<code>Context</code> level as required. Normally, this Valve would be used
at the <code>Engine</code> level.</p>
-
+
<p>If used in conjunction with Remote Address/Host valves then this valve
should be defined first to ensure that the correct client IP address is
presented to the Remote Address/Host valves.</p>
@@ -1312,19 +1312,19 @@
</attribute>
<attribute name="httpServerPort" required="false">
- <p>Value returned by <code>ServletRequest.getServerPort()</code>
- when the <strong>protocolHeader</strong> indicates <code>http</code>
+ <p>Value returned by <code>ServletRequest.getServerPort()</code>
+ when the <strong>protocolHeader</strong> indicates <code>http</code>
protocol and no <strong>portHeader</strong> is present. If not
specified, the default of <code>80</code> is used.</p>
</attribute>
<attribute name="httpsServerPort" required="false">
- <p>Value returned by <code>ServletRequest.getServerPort()</code>
- when the <strong>protocolHeader</strong> indicates <code>https</code>
+ <p>Value returned by <code>ServletRequest.getServerPort()</code>
+ when the <strong>protocolHeader</strong> indicates <code>https</code>
protocol and no <strong>portHeader</strong> is present. If not
specified, the default of <code>443</code> is used.</p>
</attribute>
-
+
<attribute name="changeLocalPort" required="false">
<p>If <code>true</code>, the value returned by
<code>ServletRequest.getLocalPort()</code> and
@@ -1342,17 +1342,17 @@
<section name="Crawler Session Manager Valve">
<subsection name="Introduction">
-
+
<p>Web crawlers can trigger the creation of many thousands of sessions as
they crawl a site which may result in significant memory consumption. This
Valve ensures that crawlers are associated with a single session - just
like
normal users - regardless of whether or not they provide a session token
with their requests.</p>
-
+
<p>This Valve may be used at the <code>Engine</code>, <code>Host</code> or
<code>Context</code> level as required. Normally, this Valve would be used
at the <code>Engine</code> level.</p>
-
+
<p>If used in conjunction with Remote IP valve then the Remote IP valve
should be defined before this valve to ensure that the correct client IP
address is presented to this valve.</p>
@@ -1397,13 +1397,13 @@
<section name="Stuck Thread Detection Valve">
<subsection name="Introduction">
-
- <p>This valve allows to detect requests that take a long time to process,
which might
+
+ <p>This valve allows to detect requests that take a long time to process,
which might
indicate that the thread that is processing it is stuck.</p>
- <p>When such a request is detected, the current stack trace of its thread
is written
+ <p>When such a request is detected, the current stack trace of its thread
is written
to tomcat log with a WARN level.</p>
- <p>The IDs of the stuck threads are available through JMX in the
- <code>stuckThreadIds</code> attribute. The JVM Thread MBean can then be
used to
+ <p>The IDs of the stuck threads are available through JMX in the
+ <code>stuckThreadIds</code> attribute. The JVM Thread MBean can then be
used to
retrieve other information about each stuck thread (name, stack
trace...).</p>
</subsection>
@@ -1422,10 +1422,10 @@
</attribute>
<attribute name="threshold" required="false">
- <p>Minimum duration in seconds after which a thread is considered
stuck.
+ <p>Minimum duration in seconds after which a thread is considered
stuck.
Default is 600 seconds. If set to 0, the detection is disabled.</p>
<p>Note: since the detection is done in the background thread of the
Container
- (Engine, Host or Context) declaring this Valve, the threshold should
be higher
+ (Engine, Host or Context) declaring this Valve, the threshold should
be higher
than the <code>backgroundProcessorDelay</code> of this Container.</p>
</attribute>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
