JunosE Software supports an embedded Web server, known as the HTTP local server, which is used to support the Service Manager application’s guided entrance service. With guided entrance, subscribers are directed to a specific Web site when they log in. At the Web site, the subscribers can then select the service they want to use. You can configure one HTTP local server per virtual router. The HTTP local server is disabled by default.
In lower-numbered releases, the HTTP server listened for and processed only IPv4 exception packets. You can now configure the HTTP local server to listen for and process both IPv4 and IPv6 packets.
![]() | Note: Currently, the HTTP local server does not support two different ports for IPv4 and IPv6 packets. However, the HTTP local server can listen for both IPv4 and IPv6 exception packets on the same port, simultaneously. |
The following topics explain how to configure the HTTP local server to support guided entrance:
To configure the HTTP local server to support guided entrance for IPv4:
Use the no version to delete the HTTP local server.
Use the no version to remove the association between the access list and the HTTP local server.
You can specify a port number in the range 1–65535. Use the no version to restore the default port number, 80.
You can specify a number in the range 0–1000.
Use the no version to restore the default number of allowed connections, 3.
You can specify a time in the range 3–7200 seconds, or 0. A value of 0 causes the server to maintain an inactive connection indefinitely. Use the no version to restore the default time, 30 seconds.
Use the no version to disable the HTTP local server.
The first access session is typically used by the Service Manager application to provide initial provisioning and service selection for the subscriber. HTTP redirect is per-interface; use the command in Profile Configuration mode for dynamic interfaces; use the command in Interface Configuration mode or Subinterface Configuration mode for static interfaces.
The redirect URL can be a maximum of 230 characters.
![]() | Note: The HTTP local server must be configured and enabled in the virtual router for the interface on which you use the ip http redirectUrl command. Otherwise, the URL redirect operation will fail. |
Use the no version to restore the default, which disables the HTTP redirect feature.
To configure the HTTP local server to support guided entrance for IPv6:
Use the no version to delete the HTTP local server.
Use the no version to remove the association between the access list and the HTTP local server.
![]() | Note: You can modify the port on which the HTTP local server receives connection attempts. However, you must first disable the HTTP local server and then modify the port. |
You can specify a port number in the range 1–65535. Use the no version to restore the default port number, 80.
You can specify a number in the range 0–1000. Use the no version to restore the default number of allowed connections, 3.
You can specify a time in the range 3–7200 seconds, or 0. A value of 0 causes the server to maintain an inactive connection indefinitely. Use the no version to restore the default time, 30 seconds.
Use the no version to disable the HTTP local server.
The first access session is typically used by the Service Manager application to provide initial provisioning and service selection for the subscriber. HTTP redirect is per-interface; use the command in Interface Configuration mode or Subinterface Configuration mode for static interfaces and use the command in Profile Configuration mode for dynamic interfaces.
The redirect URL can be a maximum of 230 characters.
![]() | Note: The HTTP local server must be configured and enabled in the virtual router for the interface on which you use the ipv6 http redirectUrl command. Otherwise, the URL redirect operation will fail. |
Use the no version to restore the default, which disables the HTTP redirect feature.