HTTP and SOAP Channels : HTTP Channel Advanced Configuration Settings

HTTP Channel Advanced Configuration Settings
The following settings configure the internal HTTP server used by the channel. They are set in the Advanced tab of the HTTP channel resource editor.
Displays the server type selected in the Channel tab: BUILT-IN or TOMCAT. Configuration options differ in each case, as shown in this table.
The number of milliseconds the HTTP server waits after accepting a connection, for the request URI line (that is, the first part of the request message) to be presented.
The value 0 means no timeout.
The maximum queue length for incoming connection requests when all request processing threads are in use. Any requests received when the queue is full are refused.
The value -1 means that a default of 10 is set.
The value -1 means that the use of a buffer is disabled.
For the BUILT-IN server, set to a positive integer value. If no value is specified, then the BUILT-IN server handles n requests simultaneously, where n is less than the maximum number of open file descriptors (sockets) for the server socket. This number depends on the operating system.
The value -1 means that the following default values are used:
If the checkbox is checked, the TCP_NO_DELAY option is not set on the server socket.
If the checkbox is checked, the TCP_NO_DELAY option is set on the server socket. Using TCP_NO_DELAY improves performance under most circumstances.
If checked, the encoding specified in the contentType HTTP header is used to decode the request URI.
The absolute path where static HTML files are stored. The HTTP server retrieves pages from this location. This setting is used by internal TIBCO BusinessEvents applications and may have limited application for other purposes.
The name of the default static HTML file stored in the document root. This setting is used by internal TIBCO BusinessEvents applications and may have limited application for other purposes.
Note  Displays only for TOMCAT Server Type but not used in this release and not specific to this server type.
The number of milliseconds during which the sockets used by the HTTP server linger (that is, not complete immediately) when they are closed. Use of socket linger allows time for a graceful shutdown sequence to complete.
Set to true if you want the calls to request.getRemoteHost() to perform DNS lookups and return the actual host name of the remote client. Set to false to skip the DNS lookup and return the IP address as a string instead (thereby improving performance).
The compression option set here is used together with the MIME types shown in the Compressible Mime Types setting. Allowable values are:
off  Disables compression. Values in the Compressible Mime Types setting are ignored.
on  Enables compression
force  Forces compression.
An integer  Specifies a threshold amount of data above which output is compressed. The unit is bytes. For example, if set to 2048 then any file above 2MB will be compressed. If content length is unknown, the output is always compressed. Compression applies to MIME types shown in the Compressible Mime Types setting that are over the threshold (or unknown.
A value of 1 disables HTTP/1.0 keep-alive, as well as HTTP/1.1 keep-alive and pipelining.
The maximum size of the POST data, specified in bytes, which is handled by the container FORM URL parameter parsing. You can disable the limit by setting this to less than or equal to 0.
The maximum size of the POST data, specified in bytes, which is saved or buffered by the container during FORM or CLIENT-CERT authentication. For both types of authentication, the POST data is saved or buffered before the user is authenticated.
For CLIENT-CERT authentication, the POST data is buffered for the duration of the SSL handshake and the buffer emptied when the request is processed.
For FORM authentication the POST is saved while the user is redirected to the login form and is retained until the user successfully authenticates or the session associated with the authentication request expires.
http  HTTP protocol.
https  For secure communications (SSL).
memory  Memory protocol.
ajp  Apache JServ Protocol, a binary protocol.
The maximum number of unused request processing threads that are allowed to exist until the thread pool starts stopping the unnecessary threads.
The number of request processing threads that are created when this Connector is first started. The connector also makes sure that it has the specified number of idle processing threads available. Set this to a value smaller than that set for Max Spare Threads.
The default value is text/html,text/xml,text/plain.
Used to limit support to specific browsers and versions of specific browsers. Comma-separated list containing one or more browser names, such as Mozilla, Internet Explorer. Prepend version with a slash, for example, Mozilla/4.0.
Disabling the stale connection check may result in slight performance improvement at a risk of getting an I/O error when executing a request over a connection that has been closed at the server side.
Defining Event Properties for Standard HTTP Header Properties
You need to define corresponding event properties for HTTP header names so that the header names are mapped to the event properties at run time.
Standard HTTP header properties can have a dash (-) in their names. While defining the corresponding event properties for such header properties, use an underscore character (_) instead of a dash(-). A dash is not allowed in the event property names.
Following is the list of the HTTP header properties. In this a dash is replaced by an underscore while converting from HTTP headers to Event Properties, and vice-versa.