Web server plug-in request and response optimization properties


To set the request and response optimization properties for a Web server plug-in.

To view this admin console page ...

Servers > Server Types > Web servers > web_server_name > Plug-in properties > Request and response .

Maximum chunk size used when reading the HTTP response body

Maximum chunk size the plug-in can use when reading the response body.

This field corresponds to the ResponseChunkSize element in plugin-cfg.xml.

The plug-in reads the response body in 64K chunks until all of the response data is read. This approach causes a performance problem for requests whose response body contains large amounts of data.

If the content length of the response body is unknown, the values specified for this property is used as the size of the buffer that is allocated. The response body is then read in this size chunks, until the entire body is read. If the content length is known, then a buffer size of either the content length or the specified size (whichever is less) is used to read the response body.

Data type Integer
Default 64 kilobytes

Specify the size in kilobytes (1024 byte blocks).

Enable Nagle algorithm for connections to the appserver

When checked, the Nagle algorithm is enabled for connections between the plug-in and the appserver.

This field corresponds to the ASDisableNagle element in plugin-cfg.xml.

The Nagle algorithm is named after engineer John Nagle, who invented this standard part of the transmission control protocol/internet protocol (TCP/IP). The algorithm reduces network overhead by adding a transmission delay (usually 20 milliseconds) to a small packet, which lets other small packets arrive and be included in the transmission. Because communications has an associated cost not as dependent on packet size as it is on frequency of transmission, this algorithm potentially reduces overhead with a more efficient number of transmissions.

By default, this field is not checked, and the Nagle algorithm is disabled. Select this field to enable the Nagle algorithm.

Enable Nagle Algorithm for the IIS Web Server

When checked, the Nagle algorithm is used for connections from the Microsoft Internet Informations Services (IIS) Web Server to the appserver.

This field corresponds to the IHSDisableNagle element in plugin-cfg.xml. It only appears if we are using the Microsoft Internet Informations Services (IIS) Web server.

By default, this field is not checked, and the Nagle algorithm is disabled. Select this field to enable the Nagle algorithm for this connection.

Chunk HTTP response to the client

When checked, responses to the client are broken into chunks if a Transfer-Encoding : Chunked response header is present in the response.

This field corresponds to the ChunkedResponse element in plugin-cfg.xml. It only appears if we are using a Microsoft Internet Informations Services (IIS) Web Server, a Java™ System Web server, or a Domino Web server. The IBM HTTP Server automatically handles breaking the response into chunks to send to the client.

By default, this field is not checked, and responses are not broken into chunks. Select this field to enable responses to the client to be broken into chunks if a Transfer-Encoding : Chunked response header is present in the response.

Accept content for all requests

This field corresponds to the AcceptAllContent element in plugin-cfg.xml.

When selected, users can include content in POST, PUT, GET, and HEAD requests when a Content-Length or Transfer-encoding header is contained in the request header.

By default, this field is not checked. Select this field to enable users to include content in POST, PUT, GET, and HEAD requests when a Content-Length or Transfer-encoding header is contained in the request header.

Virtual host matching

When selected, virtual host mapping is performed by physically using the port number for which the request was received.

This field corresponds to the VHostMatchingCompat element in plugin-cfg.xml.

By default, this field is not checked, and matching is done logically using the port number contained in the host header. Select this field if we want virtual host mapping performed by physically using the port number for which the request was received.

Use the radio buttons to make the physical or logical port selection.

Application Server port preference

Specifies which port number the appserver should use to build URIs for a sendRedirect. This field is only applicable for a sendRedirect if we use relative URIs and does not affect absolute redirects. This field also specifies where to retrieve the value for HttpServletRequest.getServerPort().

This field corresponds to the AppServerPortPreference element in plugin-cfg.xml.

Specify:

  • hostHeader if the port number from the host header of the HTTP request coming in is to be used.

  • webserverPort if the port number on which the Web server received the request is to be used.

The default is hostHeader.





 

Related tasks


Communicating with Web servers

 

Related

Object names: What the name string cannot contain
Web server plug-in properties