HTTP connection handlers are responsible for managing the communication with HTTP clients and invoking servlets to process requests from those clients, as well as host web applications on the server.
Each HTTP connection handler must be configured with one or more HTTP servlet extensions and zero or more HTTP operation log publishers.
If you cannot start the HTTP connection handler (for example, if its associated HTTP Servlet Extension fails to initialize), then this will not prevent the entire PingDirectoryProxy server from starting. The server's start-server tool will output any errors to the error log. This allows the server to continue serving LDAP requests even with a bad servlet extension. The configuration properties available for use with an HTTP connection handler include:
- Specifies the address on which the connection handler will listen for requests from clients. If not specified, then requests will be accepted on all addresses bound to the system.
- Specifies the port on which the connection handler will listen for requests from clients. This is required.
- Indicates whether the connection handler will use SSL/TLS to secure
communications with clients (whether it uses HTTPS rather than HTTP). If SSL is
trust-manager-providervalues must also be specified.
- Specifies the set of servlet extensions that will be enabled for use with the connection handler. You can have multiple HTTP connection handlers (listening on different address/port combinations) with identical or different sets of servlet extensions. At least one servlet extension must be configured.
- Specifies the set of HTTP operation log publishers that should be used with the connection handler. By default, no HTTP operation log publishers will be used.
- Specifies the key manager provider that will be used to obtain the certificate presented to clients if SSL is enabled.
- Specifies the trust manager provider that will be used to determine whether to accept any client certificates presented to the server.
- Specifies the number of threads that should be used to process requests from HTTP clients. These threads are separate from the worker threads used to process other kinds of requests. The default value of zero means the number of threads will be automatically selected based on the number of CPUs available to the Java virtual machine (JVM).
- Specifies the Web applications to be hosted by the server.