|
|
|
|
false |
Deprecated. Use the sso-enabled attribute
instead. |
|
300 |
Specifies the time after which a user’s single sign-on record becomes eligible for
purging if no client activity is received. Since single sign-on applies across several
applications on the same virtual server, access to any of the applications keeps
the single sign-on record active. Higher values provide longer single sign-on persistence for the
users at the expense of more memory use on the server. |
sso-reap-interval-seconds |
60 |
Specifies the interval
between purges of expired single sign-on records. |
|
dynamic |
Deprecated. Use the sso-cookie-secure attribute instead. |
|
none |
Specifies a
comma-separated list of Cache-Control response directives. For a list of valid directives, see
section 14.9 of the document at http://www.ietf.org/rfc/rfc2616.txt. |
|
false |
Deprecated. Use the access-logging-enabled attribute instead. |
|
32768 |
Specifies the size,
in bytes, of the buffer where access log calls are stored. If the
value is less than 5120, a warning message is issued, and the value
is set to 5120. |
|
300 |
Specifies the number of seconds before the log is
written to the disk. The access log is written when the buffer is
full or when the interval expires. If the value is 0, the buffer is
always written even if it is not full. This means that each
time the server is accessed, the log message is stored directly to the file. |
|
none |
Specifies
a comma-separated list of regular expression patterns that the remote client's IP address
is compared to. If this property is specified, the remote address must match
for this request to be accepted. If this property is not specified, all requests
are accepted unless the remote address matches a denyRemoteAddress pattern. |
|
none |
Specifies a comma-separated list
of regular expression patterns that the remote client's IP address is compared to.
If this property is specified, the remote address must not match for this request
to be accepted. If this property is not specified, request acceptance is governed
solely by the allowRemoteAddress property. |
|
none |
Specifies a comma-separated list of regular expression patterns that
the remote client's hostname (as returned by [java.net.]Socket.getInetAddress().getHostName()) is compared to. If
this property is specified, the remote hostname must match for this request to
be accepted. If this property is not specified, all requests are accepted unless
the remote hostname matches a denyRemoteHost pattern. |
|
none |
Specifies a comma-separated list of regular
expression patterns that the remote client's hostname (as returned by [java.net.]Socket.getInetAddress().getHostName()) is compared
to. If this property is specified, the remote hostname must not match for
this request to be accepted. If this property is not specified, request acceptance
is governed solely by the allowRemoteHost property. Setting this property has no effect if jk-enabled
is set to true for a network-listener. |
|
none |
Specifies the name attribute of an auth-realm
element, which overrides the server instance's default realm for stand-alone web applications deployed to
this virtual server. A realm defined in a stand-alone web application's web.xml
file overrides the virtual server's realm. |
|
true |
|
|
none |
Specifies an alternate document root (docroot), where n is
a positive integer that allows specification of more than one. Alternate docroots allow
web applications to serve requests for certain resources from outside their own docroot,
based on whether those requests match one (or more) of the URI patterns of
the web application's alternate docroots. If a request matches an alternate docroot's URI
pattern, it is mapped to the alternate docroot by appending the request URI
(minus the web application's context root) to the alternate docroot's physical location (directory). If
a request matches multiple URI patterns, the alternate docroot is determined according to
the following precedence order:
Exact match
Longest path match
Extension match
For example, the following properties specify three alternate docroots. The URI
pattern of the first alternate docroot uses an exact match, whereas the URI
patterns of the second and third alternate docroots use extension and longest path
prefix matches, respectively. <property name="alternatedocroot_1"
value="from=/my.jpg dir=/srv/images/jpg"/>
<property name="alternatedocroot_2"
value="from=*.jpg dir=/srv/images/jpg"/>
<property name="alternatedocroot_3"
value="from=/jpg/* dir=/src/images"/> The value of each alternate docroot has two components: The first
component, from, specifies the alternate docroot's URI pattern, and the second component, dir,
specifies the alternate docroot's physical location (directory). Spaces are allowed in the dir
component. You can set this property for a specific web application. For details, see
sun-web-app in Sun GlassFish Enterprise Server v3 Application Deployment Guide. |
|
none |
|
|
false |
|
|
none |
Specifies custom error page mappings for the
virtual server, which are inherited by all web applications deployed on the virtual server.
A web application can override these custom error page mappings in its web.xml
deployment descriptor. The value of each send-error_n property has three components, which may be
specified in any order: The first component, code, specifies the three-digit HTTP response status
code for which the custom error page should be returned in the response. The
second component, path, specifies the absolute or relative file system path of the
custom error page. A relative file system path is interpreted as relative to
the domain-dir/config directory. The third component, reason, is optional and specifies the text of
the reason string (such as Unauthorized or Forbidden) to be returned. For example: <property name="send-error_1"
value="code=401 path=/myhost/401.html reason=MY-401-REASON"/> This
example property definition causes the contents of /myhost/401.html to be returned with
401 responses, along with this response line: HTTP/1.1 401 MY-401-REASON |
|
none |
Specifies that a request for an old
URL is treated as a request for a new URL. These properties are
inherited by all web applications deployed on the virtual server. The value of
each redirect_n property has two components, which may be specified in any order: The
first component, from, specifies the prefix of the requested URI to match. The second
component, url-prefix, specifies the new URL prefix to return to the client. The
from prefix is simply replaced by this URL prefix. For example: <property name="redirect_1"
value="from=/dummy url-prefix=http://etude"/> |
|
none |
Specifies a fully qualified
class name of a custom valve, where n is a positive integer
that allows specification of more than one. The valve class must implement the
org.apache.catalina.Valve interface from Tomcat or previous Enterprise Server releases, or the
org.glassfish.web.valve.GlassFishValve interface from the current Enterprise Server release. For example: <property name="valve_1"
value="org.glassfish.extension.Valve"/> You can set this
property for a specific web application. For details, see sun-web-app in Sun GlassFish Enterprise Server v3 Application Deployment Guide. |
|
none |
Specifies a fully qualified
class name of a custom Catalina listener, where n is a positive integer that
allows specification of more than one. The listener class must implement the org.apache.catalina.ContainerListener
or org.apache.catalina.LifecycleListener interface. For example: <property name="listener_1"
value="org.glassfish.extension.MyLifecycleListener"/> You can set this property for a specific
web application. For details, see sun-web-app in Sun GlassFish Enterprise Server v3 Application Deployment Guide. |
|
org.apache.catalina.valves.ErrorReportValve |
Specifies a fully qualified class name of a custom
valve that produces default error pages for applications on this virtual server. Specify
an empty string to disable the default error page mechanism for this virtual server. |