Editing HTTP Listener Settings

You can edit the existing HTTP Listener settings by performing the following tasks:

Click Configuration tab to get the list of available configurations.
Click HTTP Listeners tab to view the list of configured HTTP Listeners.
Under the HTTP Listeners Name table, Click the HTTP Listener you need to edit.

You can edit both the general and security related settings for the HTTP Listener.

Editing General Settings

Click General tab to edit basic and advanced HTTP Listener settings. The following table provides a short description of each field in the page:

Table 2 Field Description > Editing HTTP Listener General Settings

Field	Description
Name	A short name for the new HTTP Listener
Port	Port for the HTTP Listener to bind and listen for incoming HTTP requests.
IP Address	A Valid IPv4 or IPv6 address. "*" implies that the HTTP Listener will listen to all IP addressed for the configured port.
Server Name	Enter the server name For example, sales.mycomp.com
Default Virtual Server	Select the virtual server from the drop down list. This action will associate the new HTTP Listener for the selected virtual server. You can associate more than one HTTP Listeners to a virtual server.
Description (Optional)	Enter a short description for your HTTP Listener.

Select the Configure Advanced Settings option under the Advanced section to edit HTTP Listener advanced settings. The following table provides a short description of each field in the page:

Table 3 Field Description > Editing HTTP Listener General Settings

Field	Description
Acceptor Threads (Required)	Number of threads dedicated to accept connections received by this listener. Accepted values are 1 to 128.
Protocol Family	The protocol used by the listener. Do not modify this value. Default is HTTP.
Listen Queue Size	Maximum size of the operating system listen queue backlog.
Receive Buffer Size	Size (in bytes) of the operating system socket receive buffer.
Send Buffer Size	Size (in bytes) of the operating system socket send buffer.
Blocking I/O	Determines if the HTTP listener socket is in the blocking mode. Disabled by default.

Editing HTTP Listener Security Settings

Note - Security can be enabled for the HTTP listener only when there are available installed certificates.

Once you have a certificate, you can associate the certificate with a HTTP Listener and thus secure the server.

Encryption is the process of transforming information so it is meaning less to anyone except the intended recipient. Decryption is the process of transforming encrypted information so that it is meaningful again. Sun Java System Web Server includes support for SSL and TLS protocols.

A cipher is a cryptographic algorithm (a mathematical function), used for encryption or decryption. SSL and TLS protocols contain numerous cipher suites. Some ciphers are stronger and more secure than others. Generally speaking, the more bits a cipher uses, the harder it is to decrypt the data.

In any two-way encryption process, both parties must use the same ciphers. Because a number of ciphers are available, you need to enable your server for those most commonly used.

During a secure connection, the client and the server agree to use the strongest cipher they can both have for communication. You can choose ciphers from the SSL2,SSL3, and TLS protocols.

Note - Improvements to security and performance were made after SSL version 2.0; you should not use SSL 2 unless you have clients that are not capable of using SSL 3. Client certificates are not guaranteed to work with SSL 2 ciphers.

The encryption process alone isn't enough to secure your server's confidential information. A key must be used with the encrypting cipher to produce the actual encrypted result, or to decrypt previously encrypted information. The encryption process uses two keys to achieve this result: a public key and a private key. Information encrypted with a public key can be decrypted only with the associated private key. The public key is published as part of a certificate; only the associated private key is safeguarded.

Server supports the Secure Sockets Layer (SSL) and the Transport Layer Security (TLS) protocols for encrypted communication. SSL and TLS are application independent, and higher level protocols can be layered transparently on them.

SSL and TLS protocols support a variety of ciphers used to authenticate the server and client to each other, transmit certificates, and establish session keys. Clients and servers may support different cipher suites, or sets of ciphers, depending on factors such as which protocol they support, company policies on encryption strength, and government restrictions on export of encrypted software. Among other functions, the SSL and TLS handshake protocols determine how the server and client negotiate which cipher suites they will use to communicate.

Click Security tab to edit HTTP Listeners security settings. The following table lists the properties that you can configure in this page.

Table 4 Field Description > HTTP Listener Security Settings

Field	Description
Name	Name of the HTTP Listener.
Security	Enable/Disable security for the selected HTTP Listener.
Certificate	Select the server certificate from the available certificates. You should have installed either a RSA or ECC certificate for performing this action.
Client Authentication	Specifies whether the client authentication is required or optional. Select False option to disable client authentication.
Authentication Timeout	Timeout after which client authentication handshake fails. [0.001-3600]. The default value is 60 seconds.
Maximum Authentication Data	Maximum amount of authentication data to buffer. [0-214704836470]. The default value is 10485706.
SSL Version 2/Version 3	Enable/Disable SSL Version 2/ SSL Version 3.
TLS	Enable/Disable TLS. Detect version rollbacks is enabled by default. This configures the server to detect man-in-the-middle version rollback attack attempts. Disabling this may be required for interoperability with some clients that incorrectly implement the TLS specification.
SSL3/SSL2/TLS Ciphers	To protect the security of your web server, you should enable SSL. You can enable the SSL 2.0, SSL 3.0, and TLS encryption protocols and select the various cipher suites. SSL and TLS can be enabled on the listen socket for the Administration Server. Enabling SSL and TLS on a listen socket for the Server Manager will set those security preferences for all virtual servers associated with that listen socket. The default settings allow the most commonly used ciphers. Unless you have a compelling reason why you don't want to use a specific cipher suite, you should allow them all.