reset-cookies-list = JSESS*,Ltpa*
response-code-rules
Syntax
response-code-rules = listDescription
The WebSEAL server performs a periodic background ping of each junctioned Web server to determine whether it is running. The optional response-code-rules configuration entry defines the rules that are used to determine whether HTTP responses indicate a healthy or an unhealthy junctioned Web server.
The configuration entry contains a space separated list of rules. Each rule has the format: [+|-]<code> (e.g. -50?)
where:
+ Indicates that this is a healthy response code.
- Indicates that this is an unhealthy response code.
<code>
The corresponding response code, which can also contain pattern matching characters such as * and ?
The HTTP response codes are evaluated against each rule in sequence until a match is found. The corresponding code (+|-) determines whether the junctioned Web server is healthy or not.If the response code matches no configured rules, the junctioned Web server is considered healthy.
You can customize this configuration item for a particular junction by adding the adjusted configuration item to a [junction:{junction_name}] stanza.
where {junction_name} refers to the junction point for a standard junction (including the leading / character) or the virtual host label for a virtual host junction.
Options
list A space separated list of response code rules. These rules determine whether the response from a junctioned Web server indicates a healthy or an unhealthy server.
Usage
This stanza entry is optional.
Default value
nil response-code-rules = +2?? -*share-cookies
Syntax
share-cookies = {yes|no}Description
The share-cookies item is used to control whether the cookie jar will be shared across different junctions or whether each junction will have a dedicated cookie jar.
Options
yes If this entry is set to yes, cookies will be sent over all junctions, regardless of the junction from which the cookie originated.
no If this entry is set to no, only cookies received from the junction will be sent in requests to that junction.
Usage
This stanza entry is required.
Default value
noExample
share-cookies = yessupport-virtual-host-domain-cookies
Syntax
support-virtual-host-domain-cookies = {yes|no}Description
If allow-backend-domain-cookies is set to yes, then this option modifies how WebSEAL validates the domain. This option has no effect if validate-backend- domain-cookies = no.
You can customize this configuration item for a particular junction by adding the adjusted configuration item to a [junction:{junction_name}] stanza.
where {junction_name} refers to the junction point for a standard junction (including the leading / character) or the virtual host label for a virtual host junction.
Options
yes If set to "yes" then the domain cookie is validated by comparing it with the virtual host specified for a backend server with the -v junction option.
no If set to "no", or if no virtual host was specified for a junction, then the fully qualified host name is compared with the domain value of a backend cookie for validation.
Usage
This stanza entry is required.
Default value
yes support-virtual-host-domain-cookies = yesuse-new-stateful-on-error
Syntax
use-new-stateful-on-error = {yes|no}Description
This configuration item may be customized for a particular junction by adding the adjusted configuration item to a [junction:{junction_name}] stanza.
where {junction_name} refers to the junction point for a standard junction (including the leading / character) or the virtual host label for a virtual host junction. For example:
[junction:/WebApp]
Options
yes When set to "yes" and the original server becomes unavailable during a session, WebSEAL directs the user's next request (containing the original stateful cookie) to a new replica server on the same stateful junction. If a new replica server is found on that stateful junction, and is responsive to the request, WebSEAL sets a new stateful cookie on the user's browser. Subsequent requests during this same session (and containing the new stateful cookie) are directed to this same new server.
no When set to "no" and the original server becomes unavailable during a session, WebSEAL does not direct the user's subsequent requests to a new replica server on the same stateful junction. Instead, WebSEAL returns an error and attempts to access the same server for subsequent requests by the user during this session.
Usage
This stanza entry is required.
Default value
noExample
use-new-stateful-on-error = yesvalidate-backend-domain-cookies
Syntax
validate-backend-domain-cookies = {yes|no}Description
Specifies how WebSEAL validates the domain.
You can customize this configuration item for a particular junction by adding the adjusted configuration item to a [junction:{junction_name}] stanza.
where {junction_name} refers to the junction point for a standard junction (including the leading / character) or the virtual host label for a virtual host junction.
Options
yes If set to "yes" then domain cookies that adhere to the cookie specification are forwarded to the user. If the fully qualified host name of the
originating back-end machine is the domain, then the cookie is forwarded to the user with no domain specified.
no If set to "no", then all domain cookies are forwarded to the user, regardless of their content.
Usage
This stanza entry is required.
Default value
yes validate-backend-domain-cookies = yesworker-thread-hard-limit
Syntax
worker-thread-hard-limit = number_of_threadsDescription
Integer value indicating the limit, expressed as a percentage, of the total worker threads that are to be used for processing requests for junctions.
Options
number_of_threads
Integer value indicating the limit, expressed as a percentage, of the total worker threads that are to be used for processing requests for junctions. The default value of 100 means that there is no limit.
When the value of worker-thread-hard-limit is less than 100, and the limit is exceeded, WebSEAL generates an error message.
Usage
This stanza entry is required.
Default value
100Example
worker-thread-hard-limit = 100worker-thread-soft-limit
Syntax
worker-thread-soft-limit = number_of_threadsDescription
Integer value indicating the limit, expressed as a percentage, of the total worker threads that are to be used for processing requests for junctions.
Options
Integer value indicating the limit, expressed as a percentage, of the total worker threads that are to be used for processing requests for junctions. When the value of worker-thread-soft-limit is less than 100, and the limit is exceeded, WebSEAL generates a warning message.
Usage
This stanza entry is required.
Default value
90Example
worker-thread-soft-limit = 90