#### To edit an HTTP listener

1. In the Developer profile, expand the Configuration, HTTP Service, and HTTP Listeners node.
2. In the Clusters and Enterprise profile, expand the Configuration node, select the configuration you want to configure, then select HTTP service, then the HTTP Listeners node.
3. Select the listener you want to edit.

   If you edit the special HTTP listener named `admin-listener`, you must restart the server for the changes to take effect. The Admin Console does not identify that a restart is required in this case.

4. Edit the HTTP Listener General Settings as follows:

   - Name: Provide a unique identifier for your new listener.

   - Listener: Remove the check from the Enabled box if you do not want to enable the listener when the server restarts.

   - Security: Check this box if you want to create a listener that is secure.

   - Network Address: Enter 0.0.0.0 if you want the listener to listen on all IP addresses for the server, using a unique port value. Otherwise, type a valid IP address for the server.

   - Listener Port: Enter a unique port value if the Network Address field is 0.0.0.0, or the desired port value if you are using another IP address.

   - Default Virtual Server: Choose a virtual server from the Default Virtual Server drop-down list.

   - Server Name: Enter the host name to be used in the URLs the server sends to the client. This name is the alias name if your server uses an alias. If your server does not use an alias, leave this field empty.

5. Edit the HTTP Listener Advanced settings as follows:

   - Redirect Port: To redirect requests to another port, type a value in the Redirect Port field. The Application Server automatically redirects the request if these two conditions exist:

     - This listener is supporting non-SSL requests.

     - A request is received for which a matching security constraint requires SSL transport.

       By default, the Application Server uses the port number specified in the original request.

   - Acceptor Threads: Change the number of Acceptor Threads.

   - Powered By: Remove the check from the Powered By box to disable the inclusion of the `X-Powered-By: Servlet/2.4` header in servlet-generated HTTP response headers.

     The Java Servlet 2.4 Specification defines this header, which containers may add to servlet-generated responses. Similarly, the JavaServer Pages (JSP) 2.0 Specification defines an `X-Powered-By: JSP/2.0` header to be added (on an optional basis) to responses that use JSP technology. The inclusion of the `X-Powered-By: JSP/2.0` header is enabled by default for web applications. The goal of these headers is to aid web site administrators in gathering statistical data about the use of Servlet and JSP technology.

     For information on enabling and disabling the `X-Powered-By` header for JSP pages, see Appendix A, Deployment Descriptor Files, in Sun Java System Application Server 9.1 Application Deployment Guide.

     Production environments might decide to omit the generation of `X-Powered-By` headers to hide their underlying technology.

6. Click Save.

###### See Also

- Configuring HTTP Listeners

- To Configure an HTTP Listener to Use SSL

- To delete an HTTP listener