If you are using an HTTP transport channel, you can add any of the following custom properties to the configuration settings for that channel.
Following is a list of the HTTP transport channel custom properties provided with WebSphere application Server. These properties are not shown on the settings page for an HTTP transport channel.
Use the CookiesConfigureNoCache property to specify whether the presence of a Set-Cookie header in an HTTP response message triggers the addition of several cache related headers. If this property is set to true, an Expires header with a very old date, and a Cache-Control header that explicitly tells the client not to cache the Set-Cookie header are added.
Data type | Boolean |
Default | False |
Use the localLogFilenamePrefix property to specify a prefix for the filename of the network log file. Normally, when inprocess optimization is enabled, requests through the inprocess path are logged based on the logging attributes set up for the Web container's network channel chain. You can use this property to add a prefix to the filename of the network log file. This new filename is then used as the filename for the log file for inprocess requests. Requests sent through the inprocess path are logged to this file instead of to the network log file. For example, if the log file for a network transport chain is named .../httpaccess.log, and this property is set to local for the HTTP channel in that chain, the filename of the log file for inprocess requests to the host associated with that chain is …/localhttpaccess.log.
Data type | String |
Use the limitFieldSize property to enforce the size limits on various HTTP fields, such as request URLs, or individual header names or values. Enforcing the size limits of these fields guards against possible Denial of Service attacks. An error is returned to the remote client if a field exceeds the allowed size.
Data type | Integer |
Default | 32768 |
Range | 50-32768 |
Use the limitNumHeaders property to limit the number of HTTP headers that can be present in an incoming message. If this limit is exceeded, an error is returned to the client.
Data type | Integer |
Default | 500 |
Range | 50 to 500 |
This property is only valid for the i5/OS and distributed platforms. Use the listenBacklog property to specify the maximum number of outstanding connect requests that the operating system will buffer while it waits for the application server to accept the connections. If a client attempts to connect when this operating system buffer is full, the connect request will be rejected. Set this value to the number of concurrent connections that you would like to allow. Keep in mind that a single client browser might need to open multiple concurrent connections (perhaps 4 or 5); however, also keep in mind that increasing this value consumes more kernel resources. The value of this property is specific to each transport.
Data type | Integer |
Default | 511 |
Use the RemoveHeaderValue property to force the removal of any server header from HTTP responses that the application server sends, thereby hiding the identity of the server program.
Data type | Boolean |
Default | False |
Use the ServerHeaderValue property to specify a header that is added to all outgoing HTTP responses if a server header does not already exist.
Data type | String |
Default | WebSphere Application Server v/x.x, where x.x is the version of WebSphere Application Server that is running on your system. |