Contents

Configuring HTTP redirect 1

About HTTP redirect 1

HTTP redirect tasks at a glance· 1

Specifying the HTTPS redirect listening port number 1

Associating an SSL server policy with the HTTPS redirect service· 1

Setting the HTTPS redirect rate limit 2

Display and maintenance commands for HTTP redirect 3

Configuring HTTP redirect

About HTTP redirect

HTTP redirect is a method to redirect users' HTTP or HTTPS requests to a specific URL.

HTTP redirect tasks at a glance

No configuration is required to redirect HTTP requests.

To redirect HTTPS requests, perform the following tasks:

1.     Specifying the HTTPS redirect listening port number

2.     (Optional.) Associating an SSL server policy with the HTTPS redirect service

3.     (Optional.) Setting the HTTPS redirect rate limit

Specifying the HTTPS redirect listening port number

About this task

The device can redirect HTTPS requests only after you specify the TCP port number on which the HTTPS redirect service listens for HTTPS requests.

Restrictions and guidelines

To avoid service unavailability caused by port conflict, do not specify a TCP port number used by a well-known protocol or used by any other TCP-based service. To display TCP port numbers that have been used by services, use the display tcp command. For more information about this command, see IP performance optimization commands in Layer 3—IP Services Command Reference.

If you perform this task multiple times, the most recent configuration takes effect.

Procedure

1.     Enter system view.

system-view

2.     Specify the HTTPS redirect listening port number.

http-redirect https-port port-number

By default, the HTTPS redirect listening port number is 6654.

Associating an SSL server policy with the HTTPS redirect service

About this task

An SSL server policy is a set of SSL parameters used by the device when the device acts as the SSL server. You can configure parameters such as supported cipher suites and whether to perform digital certificate-based authentication on SSL clients for the SSL server policy.

You can use one of the following local certificates for HTTPS redirect service according to the security requirements and the configuration complexity:

·     Self-signed certificate—Using this type of certificate is simple in configuration but has low security. You do not need to associate an SSL server policy with the HTTPS redirect service and the default SSL parameters are used. However, a self-signed certificate is not trusted by the browser. When the device redirects HTTPS requests to the specified URL, a certificate security warning prompt might appear on the browser. If you accept the security risks stated in the prompt, you can ignore the prompt to browse the page.

·     CA-signed certificate—Using this type of certificate is complex in configuration but has high security. You must obtain a CA certificate, request a local certificate from the CA, create an SSL server policy, and associate the SSL server policy with the HTTPS redirect service.

For more information about digital certificates, see PKI in Security Configuration Guide. For more information about the SSL server policy configuration, see SSL in Security Configuration Guide.

Restrictions and guidelines

HTTPS redirect is unavailable if the associated SSL server policy does not exist. You can first associate a nonexistent SSL server policy with the HTTPS redirect service and then configure the SSL server policy.

If you change the SSL server policy associated with the HTTPS redirect service, the new policy takes effect immediately.

If you perform this task multiple times, the most recent configuration takes effect.

Procedure

1.     Enter system view.

system-view

2.     Associate an SSL server policy with the HTTPS redirect service.

http-redirect ssl-server-policy policy-name

By default, no SSL server policy is associated with the HTTPS redirect service. The HTTPS redirect service uses the self-assigned certificate and the default SSL parameters.

Setting the HTTPS redirect rate limit

About this task

Redirecting a large number of HTTPS requests will overwhelm the CPU and affect other services on the device. To resolve this issue, you can limit the rate of HTTPS redirect packets sent to the CPU. When the rate of the HTTP redirect packets exceeds the limit, the device drops the exceeding HTTPS redirect packets.

Restrictions and guidelines

Setting this limit affects the performances of services that need to redirect HTTPS requests, for example, the user online rate of the authentication service. Set a proper HTTPS redirect rate limit according to the network condition.

Procedure

1.     Enter system view.

system-view

2.     Set the HTTPS redirect rate limit.

http-redirect https-rate-limit pps

The default HTTPS redirect rate limit is not set.

Display and maintenance commands for HTTP redirect

Execute display commands in any view and reset commands in user view.

‌