Installation guide

New features in version 4.1.2
60 EAServer
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
Web application authentication
“None” is no longer a Web application authentication option. The default
authentication mechanism for a Web application is “HTTP Basic
Authentication”. Since Web Applications implement lazy authentication, if
you want to authenticate your client, you must associate a role with a Web
resource. The authentication options are:
• HTTP Basic
• Form authentication
• SSL mutual authentication
See Chapter 3, “Using Web Application Security,” in the EAServer Security
Administration and Programming Guide for more information.