For information on configuring the Web server redirector plug-ins, see the EAServer Installation Guide for your platform. Beginning in EAServer 4.1.2, these configuration options are now available for the Apache, iPlanet, and Netscape redirector plug-ins:
Binding to a single server You can bind a redirector to a specific server so that if the server fails to respond to a request, the redirector returns immediately. By default, a request fails over to another server when the initial server does not respond. If you are running Web applications that are not marked distributable, you must bind the redirector to a specific server. If the redirector is bound to a server and the server fails to respond to a request, the redirector returns the error status to the client.To bind the redirector to a server, add this line to the redirector configuration file, where serverName is the name of the server:
Connector.BindToServer /serverName
Debugging To trace requests from connectors, set this directive in the redirector configuration file:
Connector.SessionId <ConnectorSessionId>
When this directive is set, the connector appends the value of ConnectorSessionId to the URL that is forwarded to EAServer. EAServer writes the URL to the server’s HTTP request log, which can be helpful for debugging. For example, if you add this directive to the redirector configuration file:
Connector.SessionId ConnSID
EAServer writes this information to the HTTP request log:
10.22.85.66 - - [28/May/2002:12:11:09 -0800] “GET /TestHTTPS/?ConnSID=2696_000000000000 HTTP/1.0” 200 51 10.22.85.66 - - [28/May/2002:12:11:24 -0800] “GET /TestHTTPS/?ConnSID=2888_000000000000 HTTP/1.0” 304 0 10.22.85.66 - - [28/May/2002:12:11:40 -0800] “GET /TestHTTPS/?ConnSID=2889_000000000000 HTTP/1.0” 304 0 10.22.85.66 - - [28/May/2002:12:11:40 -0800] “GET /TestHTTPS/?ConnSID=2888_000000000001 HTTP/1.0” 304 0 10.22.85.66 - - [28/May/2002:12:11:40 -0800] “GET /TestHTTPS/?ConnSID=2889_000000000001 HTTP/1.0” 304 0
In this example, the Apache Web server process 2696 sent one request, process 2888 sent two requests, and process 2889 sent two requests. The connector session ID is computed as:
process identifier of the Web server’s process + request count
