Previous Topic: Use the HTTP HOST Request for the Port Number

Next Topic: Restrict IPC Semaphore-Related Message Output to the Apache Error Log

Use Legacy Applications with an Apache Web Agent

If you have legacy applications (that do not support HTTP 1.1), and you want to run them on an Apache Web Server, you can set the following parameter:

LegacyTransferEncodingBehavior

Specifies the type of message encoding used by the Web Agent. When the value of this parameter is set to no, transfer-encoding is supported.

When the value of this parameter is set to yes, content encoding is used. The transfer-encoding header is ignored and only the content-length header is supported.

Default: No

To use legacy applications with an Apache Web Server, set the value of the LegacyTransferEncodingBehavior parameter to yes.

Important! If you set the value of this parameter to yes, these features will not work: Federation; preservation of POST data longer than 4 KB; and large certificates may not be recognized.