You can add the following custom properties to the configuration settings for an HTTP proxy server.
Data type | Boolean |
Default | false |
Data type | Boolean |
Default | false |
Data type | Boolean |
Default | false |
Specifies whether the default proxy cache key generator uses both the URL path and query string information to generate the cache key. To enable this function, set the custom property to true. However, if you enable Edge Side Include (ESI) caching on the proxy server, this custom property is not used. If you do not set this custom property, the proxy server generates a cache key based on the URL path only and not based on the query string information.
For more information on ESI caching, see Configuring Edge Side Include caching.
Data type | String |
Specifies, in bytes, the maximum size of a cacheable response.
Because it is hard to control the total memory used by the proxy cache, out-of- memory conditions in the proxy native space can occur if the proxy server caches a lot of large responses. If you specify a value for this property, any responses that are larger then this value are not cached.
Data type | Integer |
Specifies whether the proxy server should try to correct the value in the location header when a 302 response is returned from the generic server cluster.
If you specify none for this property, the proxy server never tries to correct the value in the location header when a 302 response is returned.
If you specify gsc for this property, the proxy server tries to correct the value in the location header only when the 302 response is returned from the generic server cluster.
If you specify managed for this property, the proxy server tries to correct the value in the location header only when the 302 response is returned from a managed server.
If you specify all for this property, the proxy server tries to correct the value in the location header whenever a 302 response is returned.
Data type | String |
Acceptable values | none, gsc, managed, or all |
Default | gsc |
Data type | A comma-separated string of HTTP header names |
Data type | Boolean |
Default | false |
Data type | Boolean |
Default | false |
Specifies whether the proxy should unchunk, and buffer the response for an HTTP 1.0 client. If the http.isDisable10ResponseCaching property is set to true, the proxy server does not generate the content length header, and does not include chunked data in the client side response. Instead, the proxy server closes the connection at the end mark of the response body.
Data type | Boolean |
Default | false |
Specifies under what conditions a proxy server buffers a response for heartbeat applications.
The value of the property is a comma-separated URL pattern, such as /application_a/.*html;/application_b/.*html. For example, if the proxy server receives a /application_a/heartbeat.html request, which matches one of the URI patterns in the custom property, the proxy server does not buffer the response body for the request. In this example, if the proxy server returns a byte, it forwards the byte to the client side without buffering.
Enables you to increase the number of history files for the proxy server log files.
The proxy server log files are the proxy.log, local.log, and cache.log files. Without this custom property, you have one history file for these proxy server log files.
Data type | Boolean |
Default | 1 |
Specifies the maximum size of a chunked response, for which the proxy server will generate a content-length header.
When the proxy server receives a chunked response for an HTTP 1.0 client, the proxy server assumes that the HTTP 1.0 client cannot handle the chunked message, and tries to un-chunk the message, and calculate the content length for the response body. If the size of the chunked response is equal to, or less than the size limit specified for this property, the proxy server generates a content-length header for the response. If the chunked response exceeds the size limit specified for this property, the proxy returns a 500 error message.
Data type | integer |
Default | 100000 bytes |
Specifies the amount of time, in seconds, for the HTTP proxy server to wait during server startup before routing information. The proxy server waits for the specified number of seconds before binding its ports.
Data type | String |
Default | 150 |
Specifies the estimated time interval, in milliseconds, after which PMI statistics are recorded in the proxy server.
Data type | Integer |
Default | 100 |
Specifies the HTTP method name, which is commonly HEAD, GET for the methods used. The HTTP method name is also the advisor method set on the front end load balancer. The custom property is enabling the proxy to match incoming requests and determine whether the requests are from the load balancer or not.
Data type | String value (HTTP method name, such as GET or READ) |
Default | none |
Specifies the HTTP Advisor start up delay in seconds. The default value is 0 seconds.
If current proxy start time is less than the value defined in the HTTPProxyAdvisorStartupDelay custom property, an HTTP 503 error code is returned directly from the proxy server to inform the load balancer that the proxy/backend servers are not ready to service HTTP requests.
If current proxy start time is greater than the value defined in the HTTPProxyAdvisorStartupDelay custom property, the proxy forwards the advisor request to the backend and returns the response back to the front end load balancer. Based on the status code returned from the back-end server, the front end load balancer determines whether the proxy/backend server(s) are ready to service requests.
If the proxy is shutting down, the proxy server returns a 503 error code for the advisor requests. This error code informs the load balancer that the proxy and the backend servers are not able to service further requests and the front end load balancer needs to stop sending requests to this proxy server.
Data type | Integer (time in seconds) |
Default | 0 |
Specifies a fully qualified URI string. This is also the advisor URI set on the front end load balancer. An application on the back-end server must be configured to answer this request URI. The custom property is enabling the proxy to match incoming requests and determine whether the requests are from the load balancer or not.
Data type | String value (fully qualified URI) |
Default | none |
Specifies the front end load balancer user agent name. This custom property is enabling the proxy to match incoming requests and determine whether the requests are from the load balancer or not.
Data type | String value (HTTP User-Agent header value) |
Default | none |
Determines whether or not the host header is rewritten for content that is not on a WebSphere® Application Server content server.
Data type | Boolean |
Default | false |
Specifies the server port mapping information that the backend server uses to send responses back to the correct external Web site ports.
When port mapping information is configured on a load balancer that is sitting in front of the proxy server, the proxy server might not be able to forward the correct external Web site port information to the backend server because the external Web site port number is probably different from the Web server plug-in, or proxy server listening port. You can use this custom property to correct the port information before the proxy server passes it on to the backend server.
Name: http.virtual.port.map Value: 20080:80;20443:443
Data type | String value of port mapping pairs separated by semicolons |
Default | none |