Create an HTTP policy

There is no limit to the number of HTTP policies in a rule or the number of conditions in an HTTP policy.

Control panel

1. In the control panel, in the top menu, click Products and select Cloud Servers.

2. Go to the Load Balancers section → Load Balancers tab.

3. Open the load balancer page.

4. Open the rule card.

5. Click Add new policy.

6. Select the parameter by which the request will be checked: HOSTNAME for a domain name or PATH to check the path.

7. Select the match type for the control value:

   • EQUAL TO — matches;
   • STARTS WITH — starts with;
   • ENDS WITH — ends with;
   • CONTAINS — contains;
   • REGEX — regular expression.

8. Enter the check value. If you selected the REGEX condition in step 7, enter a regular expression.

9. Optional: to add another condition to the policy, click New condition and configure it. If there are multiple conditions in a policy, a request must match each of them to fall under the policy.

10. Specify where to redirect a matching request:

    • Forward to target group — select a target group or create a new one with the HTTP protocol;
    • Redirect to URL — enter the target URL that will completely replace the request URL, including the protocol, domain name, path, and query parameters;
    • Redirect to URL prefix — enter the part of the URL to replace the protocol and domain name in request URLs with. For example, if you enter https://example.com/new, a request to https://example.com/api will be redirected to https://example.com/new/api

    To reject requests matching the policy, select Reject traffic.

11. Enter a name for the policy or leave the default one.

12. Click Add.

OpenStack CLI

1. Open the OpenStack CLI.

2. Create an HTTP policy in the listener:

   openstack loadbalancer l7policy create \
     --action <action> \
     [--redirect-url <url> | --redirect-prefix <prefix_url> | --redirect-pool <pool> ]
     --position <position> \
     --name <policy_name> \
     <listener>

   Specify:

   • <action> — traffic balancing action:

     • REDIRECT_TO_URL — completely replace the request URL, including protocol, domain name, path, and parameters;
     • REDIRECT_PREFIX — replace the protocol and domain name in the request URL;
     • REDIRECT_TO_POOL — forward to a target group,
     • REJECT — reject;

   • <policy_name> — L7 policy name;

   • where to direct traffic:

     • --redirect-url <url> — full redirect URL. Specify if the REDIRECT_TO_URL action is selected;
     • --redirect-prefix <prefix_url> — URL prefix to replace the protocol and domain in the request with, for example, https://example.com. Specify if the REDIRECT_PREFIX action is selected;
     • --redirect-pool <pool> — ID or name of the target group. Specify if the REDIRECT_TO_POOL action is selected. You can view the list using the openstack loadbalancer pool list command. If you do not have a target group yet, create one.

   • --position <position> — position of the policy in the listener. Specify if there are multiple policies with the same action in the listener; the policy with position 1 will be applied first;

   • <listener> — ID or name of the listener. You can view the list using the openstack loadbalancer listener list command.

3. Create a condition in the HTTP policy:

   openstack loadbalancer l7rule create \
     --compare-type <compare_type> \
     --type <type> \
     --value <value> \
     <policy>

   Specify:

   • <compare_type> — match type against the check value:

     • EQUAL TO — matches;
     • STARTS WITH — starts with;
     • ENDS WITH — ends with;
     • CONTAINS — contains;
     • REGEX — regular expression;

   • <type> — request parameter to check: HOST_NAME, PATH, COOKIE, FILE_TYPE, HEADER;

   • <value> — check value;

   • <policy> — ID or name of the L7 policy created in step 2.