In the tree component, expand the Configurations node.
Select the instance to configure:
Select the HTTP Service node.
On the HTTP Service page, you can set properties that apply to all of the service’s HTTP listeners.
The following table lists these properties.
Property Name |
Description |
Default Value |
---|---|---|
If set to true, enables the TRACE operation. Set this property to false to make the Application Server less susceptible to cross-site scripting attacks. |
false |
|
If set to true, the Application Server caches local values of the statistics of the HTTP Service to answer statistics queries. This value improves performance. If set to false, the Application Server queries the HTTP Service for each statistics value. |
true |
|
Specifies the time interval, in milliseconds, after which the monitoring cache is refreshed. |
5000 |
|
Specifies the number of SSL sessions that can be cached. There is no upper limit. |
10000 |
|
Specifies the number of seconds before an SSL2 session times out. |
100 |
|
Specifies the number of seconds before an SSL3 session times out. |
86400 |
|
Specifies the maximum amount of application data, in bytes, that is buffered during the client certificate handshake phase. |
1048576 |
|
Specifies the number of seconds before the client certificate handshake phase times out. |
60 |
|
Specifies the desired keep-alive latency (in milliseconds). |
100 |
|
Specifies the upper limit to the time slept (in milliseconds) after polling keep-alive connections for further requests. |
100 |
|
Specifies the maximum stack size of the native thread. |
OS/Machine dependent |
|
If set to false, disables the recording of monitoring statistics by the HTTP Service, which improves performance. If this property is set to false, enabling monitoring for the HTTP service has no effect. |
true |
|
Specifies the default buffer size, in bytes, for unchunking request data. |
8192 |
|
Specifies the default timeout (in seconds) for unchunking request data. |
60 |
|
If set to true, allows the user to monitor statistics related to DNS caching. This property takes effect only if the DNS Lookup box on the HTTP Protocol tab is selected. Otherwise, the property setting is ignored. |
false |
Click the Access Log tab to configure access log rotation.
Click the other tabs to configure request processing, the Keep-Alive subsystem, the connection pool, the HTTP protocol, and the HTTP file cache.
Click Save.
Use this page to enable and configure rotation for the access logs for the virtual servers. These logs are in the domain-dir/logs/access directory and are named as follows: virtual-server-name_access_log%YYYY;%MM;%DD-%hh;h%mm;m%ss;s.
Click Default to load the default values.
Check the File Rotation box to turn on file rotation.
By default, file rotation is enabled.
From the Rotation Policy drop-down list, choose a policy.
The only policy available is time.
In the Rotation Interval field, type a numeric value to specify the number of minutes between rotations of the access log.
This field is valid only if the Rotation Policy is time. The default is 1440 minutes.
In the Rotation Suffix field, type a string value to specify the suffix to be added to the log file name after rotation.
The default is %YYYY;%MM;%DD;-%hh;h%mm;m%ss;s.
In the Format field, enter a string value to specify the format of the access log.
Use the formats shown in the following table. The default format is %client.name% %auth-user-name% %datetime% %request% %status% %response.length%.
Data |
Token |
---|---|
Client Host Name |
%client.name% |
Client DNS |
%client.dns% |
System Date |
%datetime% |
Full HTTP Request line |
%request% |
Status |
%status% |
Response Content Length |
%response.length% |
Referer Header |
%header.referer% |
User-agent |
%header.user-agent% |
HTTP Method |
%http-method% |
HTTP URI |
%http-uri% |
HTTP Query String |
%query-str% |
HTTP Protocol Version |
%http-version% |
Accept Header |
%header.accept% |
Date Header |
%header.date% |
If-Modified-Since Header |
%header.if-mod-since% |
Authorization Header |
%header.auth% |
Any valid HTTP header value defined in RFC 2616 (any is also a valid header value; it is specified as a variable here) |
%header.any% |
Name of Authorized User |
%auth-user-name% |
Value of a Cookie |
%cookie.value% |
Virtual Server ID |
%vs.id% |
Click Save to save the changes, or Load Defaults to return to the default settings.
Click Load Defaults to load the default values.
In the Thread Count field, type a numeric value to specify the maximum number of request processing threads.
The default is 128.
In the Initial Thread Count field, type the number of request processing threads that will be available when the server starts.
The default is 48.
In the Thread Increment field, type the number of request processing threads to be added when the number of requests exceeds the initial thread count.
The default is 10.
In the Request Timeout field, type the number of seconds after which requests will time out.
The default is 30 seconds.
In the Buffer Length field, type the size (in bytes) of the buffer used by the request processing threads to read the request data.
The default is 4096 bytes.
Click Save to save the changes, or Load Defaults to return to the default settings.
Click Load Defaults to load the default values.
In the Thread Count field, type the number of keep-alive threads to be used.
The default is 1.
In the Max Connections field, type the maximum number of persistent connections to be maintained.
The default is 256.
In the Time Out field, type the maximum number of seconds for which a keep-alive connection should be kept open.
The default is 30 seconds.
Click Save to save the changes, or Load Defaults to return to the default settings.
Click Load Defaults to load the default values.
In the Max Pending Count field, type the maximum number of pending connections to be allowed for an HTTP listener.
The default that the Application Server software specifies is 4096.
The actual value for the default maximum pending count depends
on the operating system. For example, for the Solaris operating system (OS),
the default maximum pending count is determined by the tcp_conn_req_max_q
kernel parameter of the TCP driver. The value of this parameter
is 128. To determine the default maximum pending count on the Solaris OS,
type the command ndd /dev/tcp tcp_conn_req_max_q.
In the Queue Size field, type the maximum number of outstanding connections the server can have
The default is 4096.
In the Receive Buffer Size field, type the size of the receive buffer for an HTTP listener.
The default is 4096.
In the Send Buffer Size field, type the size of the send buffer for an HTTP listener.
The default is 8192.
Click Save to save the changes, or Load Defaults to return to the default settings.
Click Load Defaults to load the default values.
In the Version field, type the version of the HTTP protocol to be used (HTTP/1.0 or HTTP/1.1).
The default is HTTP/1.1.
Select the DNS Lookup box to enable lookup of the DNS entry for the client.
The default is false.
Remove the check from the SSL box to disable security in the server globally.
Leave this value set to true to be able to use SSL for any listener that has security enabled. The default is true.
In the Forced Response Type field, type the response type to be used if there is no MIME mapping available matching the extension.
The default value is text/html; charset=iso-8859-1.
In the Default Response Type field, type the default response type.
The default value is text/html; charset=iso-8859-1. The value is a semicolon-delimited string consisting of content-type, encoding, language, and charset.
Click Save to save the changes, or Load Defaults to return to the default settings.
The file cache stores static content so that the server handles requests for such content quickly.
Click Load Defaults to load the default values.
Check the Globally box to enable file caching.
The default is true.
Check the File Transmission box to enable the use of the TransmitFileSystem method on Windows.
The default is false.
In the Max Age field, type the maximum age, in seconds, of a valid cache entry.
The default is 30 seconds.
In the Max Files Count field, type the maximum number of files in the file cache.
The default is 1024.
In the Hash Init Size field, type the initial number of hash buckets.
The default is zero.
In the Medium File Size Limit field, type the maximum size, in bytes, of a file that can be cached as a memory mapped file.
The default is 537,600 bytes.
In the Medium File Size field, type the total size, in bytes, of all files that are cached as memory mapped files.
The default is 10,485,760 bytes.
In the Small File Size Limit field, type the maximum size, in bytes, of a file that can be read into memory.
The default is 2048 bytes.
In the Small File Size field, type the total size, in bytes, of all files that are read into memory.
The default is 1,048,576 bytes.
Choose ON or OFF from the File Caching Enabled drop-down list to enable or disable caching of file content if the size of the file is less than the medium file size limit.
The default is ON.
Click Save to save the changes, or Load Defaults to return to the default settings.