HTTP transport channel custom properties

If you are using an HTTP transport channel, you can add any of the following custom properties to the configuration settings for that channel.

You can add the custom properties for an application server or a proxy server through the administrative console.

Complete the appropriate set of steps in the following list depending on the type of chain that you are creating:
  • Create a transport channel for an application server
    1. Click Servers > Application servers > server_name .
    2. Under Container Settings, expand Web Container Settings and click Web container transport chains.
    3. Under Transport Channels, click HTTP Inbound Channel (HTTP_1).
    4. Under Additional properties, click Custom Properties > New .
    5. Under General Properties specify the name of the custom property in the Name field and a value for this property in the Value field. You can also specify a description of this property in the Description field.
    6. Click Apply or OK.
    7. Click Save to save your configuration changes.
    8. Restart the server.
  • Create a transport channel for a proxy server
    1. Click Servers > Proxy Servers > server_name .
    2. Under Proxy Settings, expand HTTP Proxy Server Settings.
    3. Click Proxy server transports .
    4. Click either HTTPS _PROXY_CHAIN or HTTP _PROXY_CHAIN.
    5. Click HTTP proxy inbound channel (PROXY_1) or HTTP proxy inbound channel (PROXY_2).
    6. Under Additional properties, click Custom Properties > New .
    7. Under General Properties specify the name of the custom property in the Name field and a value for this property in the Value field. You can also specify a description of this property in the Description field.
    8. Click Apply or OK.
    9. Click Save to save your configuration changes.
    10. Restart the server.

Following are the descriptions of the HTTP transport channel custom properties provided with the product. These properties are not shown on the settings page for an HTTP transport channel.

CookiesConfigureNoCache

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 automatically added to a response message. These headers are not automatically added if this property is set to false.

This property is functionality equivalent to the com.ibm.websphere.cookies.no.header property that was available in previous versions of the product.

Data type Boolean
Default True

EnableBuildBackupList [Fix Pack 37 or later]

Use the EnableBuildBackupList property to enable the HTTP channel to scan for the history files in the access and error logs directory, and rolling these files over with any newer log files created.

When this property is set to true, the HTTP Channel scans for the history files in the access and error logs directory, and rolls these files over with any newer log files created.

Avoid trouble Avoid trouble:
  • After you configure the HTTP error log and the NCSA access log, make sure that the Enable NCSA access logging field is selected for the HTTP channels for which you want logging to occur. To verify that this field is selected for an HTTP channel, click Servers > Application Servers > server > Web Container Transport Chains > HTTP Inbound Channel. This setting has to be enabled before setting this custom property to true has any effect on the HTTP channel functionality.
  • [Updated in March 2012] If you use this custom property you must also ensure that the Use chain-specific logging option is selected as part of your configuration settings for NCSA access logging. By default, the Use global logging service option is selected for NCSA access logging. [Updated in March 2012]
    mar2012
gotcha
Data type Boolean
Default False

HonorTransferEncoding [Fix Pack 37 or later]

Use the HonorTransferEncoding property to indicate whether the HTTP transport channels should convert a chunked message to a content-length delimited message when there is only one chunk.

When this property is set to true, the HTTP transport channels write out the chunks instead of switching to a content-length message even if the message only consists of one chunk. There is a performance impact to this setting because the HTTP transport channels does two writes for every single-chunk message: the first write is for the message, and the second write is for the zero byte chunk that marks the end of the message

When this property is set to false, the HTTP transport channels convert a chunked message to a content-length delimited message when there is only one chunk. This setting improves channel performance because the channel only does one write for a single-chunk message that is converted to a content-length message.

Data type Boolean
Default False

localLogFilenamePrefix

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.

Avoid trouble Avoid trouble: If you specify a value for the localLogFilenamePrefix custom property, you must also set the accessLogFileName HTTP channel custom property to the fully qualified name of the log file you want to use for in process requests. You cannot specify a variable, such as $(SERVER_LOG_ROOT), as the value for this custom property.gotcha
Data type String

limitFieldSize

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

limitNumHeaders

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 if you are running on Version 6.1.0.33 or earlier, or 50 to 4000 if you are running on version 6.1.0.35 or later.

RemoveServerHeader

Use the RemoveServerHeader 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

ServerHeaderValue

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.



Related tasks
Configuring transport chains
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 6:03:36 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-iseries&topic=rrun_chain_httpcustom
File name: rrun_chain_httpcustom.html