Advanced Forwarding

• Description

  Route requests based on the domain name.

  • You can configure multiple domain names in a forwarding policy. Each domain name contains at least two labels separated by periods (.). Max total: 100 characters. Max label: 63 characters.
  • Each label can contain letters, digits, hyphens (-), periods (.), and asterisks (*). A label must start with a letter, digit, or asterisk (*) and cannot end with a hyphen (-). An asterisk (*) must be used as the leftmost label if you want to configure a wildcard domain name.

Example
Request URL: https://www.example.com/login.php?locale=en-us=#videos
Domain name in the forwarding rule: www.example.com

• Description

  Route requests based on paths. You can configure multiple paths in a forwarding policy. Each path contains 1 to 128 characters, including letters, digits, and special characters: _~';@^-%#$.*+?,=!:|\/()[]{}

• Matching rules
  • Exact match: The request path must exactly match that specified in the forwarding policy. The URL must start with a slash (/) and can use asterisks (*) and question marks (?) as wildcards.
  • Prefix match: The request path starts with the specified path string. The URL must start with a slash (/) and can use asterisks (*) and question marks (?) as wildcards.
  • Regular expression match: The URLs are matched using a regular expression.

Example path:
Request URL: https://www.example.com/login.php?locale=en-us#videos
Path in the forwarding rule: /login.php

A query string consists of a key and one or more values. You need to set the key and values separately.

• The key can contain only letters, digits, and special characters: !$'()*+,./:;=?@^-_'
• Multiple values can be configured for a key. The value can contain letters, digits, and special characters: !$'()*+,./:;=?@^-_'. Asterisks (*) and question marks (?) can be used as wildcard characters.

Example
Request URL: https://www.example.com/login.php?locale=en-us#videos
A query string needs to be configured for the forwarding rule:
Key: locale
Value: en-us

• You can configure multiple request methods in a forwarding policy.
• The following methods are available: GET, POST, PUT, DELETE, PATCH, HEAD, and OPTIONS.

Example
GET

An HTTP header consists of a key and one or more values. You need to configure the key and values separately.

• The key can contain only letters, digits, underscores (_), and hyphens (-).
  NOTE:

  The first letter of HTTP request headers User-agent and Connection must be capitalized.

• Multiple values can be configured for a key. The value can contain letters, digits, and special characters: !#$%&'()*+,.\/:;<=>?@[]^-_'{|}~. Asterisks (*) and question marks (?) can be used as wildcard characters.

Example
Key: Accept-Language
Value: en-us

Configure at least one of the following components:

• Protocol: ${protocol}, HTTP, or HTTPS ${protocol}: retains the protocol of the request.
• Domain Name: A domain name consists of at least two labels separated by periods (.). Each label can contain only letters, digits, hyphens (-), and periods (.), must start with a letter, digit, or asterisk (*), and cannot end with a hyphen (-). ${host}: retains the domain name of the request.
• Port: ranges from 1 to 65535. ${port}: retains the port number of the request.
• Path: A path can contain letters, digits, and special characters: _~';@^-%#&$.*+?,=!:|\/()[]{} and must start with a slash (/). ${path}: retains the path of the request.
  NOTE:

  If you select regular expression match, the request path will be overwritten by the variables that match the regular expressions. For details, see Path Matching Based on Regular Expressions.

• Query String: A query string can contain only letters, digits, and special characters: !$'()*+,./:;=?@&^-_',&. Ampersands (&) can only be used as separators.
• HTTP Status Code: 301, 302, 303, 307, or 308

Example
URL for redirection: http://www.example1.com/index.html?locale=en-us#videos
Protocol: HTTP
Domain name: www.example1.com
Port: 8081
Path: /index.html
Query String: locale=en-us
HTTP Status Code: 301

Configure the following components:

• HTTP Status Code: By default, 2xx, 4xx, and 5xx status codes are supported.
• Content-Type: text/plain, text/css, text/html, application/javascript, or application/json
• Message Body: This parameter is optional. The value is a string of 0 to 1,024 characters.

Sorry, the language is not supported.

<head><style type="text/css">div {background-color:red}#div {font-size:15px;color:red}</style></head>

<form action="/" method="post" enctype="multipart/form-data"><input type="text" name="description" value="some text"><input type="file" name="myFile"><button type="submit">Submit</button></form>

String.prototype.trim = function() {var reExtraSpace = /^\s*(.*?)\s+$/;return this.replace(reExtraSpace, "$1")}

{ "publicip": { "type": "5_bgp","ip_version": 4},"bandwidth": {"name": "bandwidth123","size": 10,"share_type": "PER"}}

Configure the following parameters:

• Domain Name: A domain name consists of at least two labels separated by periods (.). Each label can contain only letters, digits, hyphens (-), and periods (.), must start with a letter, digit, or asterisk (*), and cannot end with a hyphen (-). ${host}: retains the domain name of the request.
• Path: A path can contain letters, digits, and special characters: _~';@^-%#&$.*+?,=!:|\/()[]{} and must start with a slash (/). ${path}: retains the path of the request.
  NOTE:

  If you select regular expression match, the request path will be overwritten by the variables that match the regular expressions. For details, see Path Matching Based on Regular Expressions.

• Query String: A query string can contain only letters, digits, and the following special characters: !$'()*+,./:;=?@&^-_', and ampersand (&) can only be used as a separator.

• Matching condition: /test/(.*)/(.*)/index
• Request path: /test/ELB/elb/index

• Path: /$1/$2
• Extracting content

  $1: ELB

  $2: elb

• Destination path: /ELB/elb