平安云|Ping An Cloud- Building Your Smart Future

Configure a URL Forwarding Policy

You can configure a URL forwarding policy for an ELB instance configured with a seven-layer (HTTP and HTTPS protocol) listener to forward requests from different domain names or URLs to a specified pool. Overview For HTTP or HTTPS listener of external ELB instances, you can choose to configure the URL forwarding policy. After users create an ELB instance, as long as users has created a seven-layer (HTTP and HTTPS protocol) listener and specified a pool for the listener, namely the listener is in the state of the configured pool, it can use the domain name URL forwarding function. Listeners that do not specify a resource pool cannot be configured for URL forwarding. The four-layer listener TCP/UDP does not support URL rule forwarding. Dependency and Linkage 1. When a listener is bound to a resource pool, the resource pool will be emptied and deleted if the host member is forcibly released. The system will delete all forwarding policies at the same time. Because a listener which is "unconfigured" with resource pool cannot complete the URL forwarding process. Deleting URL policy forwarding entries will not affect the status of the listener. You only need to re-edit the listener and bind the listener to a new pool before you use it. 2. If the host member is forcibly released in the pool specified in the forwarding policy, causing the pool to be emptied and deleted. The system will delete all forwarding policies at the same time. Because a URL policy entry which is "unconfigured" with resource pool cannot take effect. Deleting URL policy forwarding entries will not affect the status of the listener. 3. In the creation of the URL forwarding policy, if you edit different URL forwarding entries for the same domain name for multiple times, the system will automatically categorize the entries under the same domain name when displayed to make your searching more convenient. 4. The policy entry first matches the standard domain name policy, and then matches the pan-resolved domain name composed of regular expressions. URL Forwarding Policy Rule If you need to enable policy forwarding, you need to enter at least the domain name policy or URL policy or both of them. Domain Usage Rule • URL forwarding supports two domain name forwarding policies: Extensive[AD1]  resolve domain name and standard domain name. Domain names with asterisk (*) are Extensive[AD2]  resolved domain names, and the standard domain name example is "yun.pingan.com." • Asterisk (*) must be the first character that appears. For example "*.pingan.com" or "*xxx.pingan.com." • Asterisk (*) cannot be used repeatedly, for example, "**.pingan.com" is not allowed. • Asterisk (*) cannot be the last character, for example, "yun.pingan.*" is not allowed. URL Usage Rule • You do not need to enter "URL". The system default URL as slash (/). • The URL input length is limited to 0-80 characters. • The URL can only use letters, numbers, en dash (-), slash (/), point (.), percent (%), question mark (?), hashtag (#), ampersand (&) and other characters. • The URL cannot be just slash (/), but it must start with slash (/). Slash (/) has been fixed at the front of the field and does not need to be entered separately. URL Forwarding Policy Limits and Quotas 1. You can edit 10 policies at a time on the creating page for submission (the slash (/) default path generated by the system by default does not need editing.) 2. Each listener can create and configure 40 URL forwarding policies (including the slash (/) default path generated by the system by default) Prerequisites You have successfully created an external ELB HTTP or HTTPS listener and bound it to a resource pool. Procedures 1. Log in to the <a href="https://pinganyun.com/console/loadBalance/overview" target="_blank">ELB Console</a>. 2. In the left navigation pane, click Instance Management to enter the Instance Management page. 3. Select the target region to view the existing ELB instances of that region. 4. Click the Instance Name of the target ELB instance and enter the Instance Information page. 5. Click the Listener tab. 6. Click Url Forward in the Operation column of the target listener.  7. Enter the domain name and URL, specify the forwarding resource pool, add a note (optional), click Add Entry, and you will see an Operation succeeded message at the bottom of the page, indicating that the configuration takes effect. <img src="https://obs-cn-shanghai.yun.pingan.com/pcp-portal/20201607142040-11d7e70e92d4.png" style="height:20px; margin:1px; width:50px" />: The default entry slash (/) is an entry automatically generated by the system which is a default policy. When the access request related to the domain name does not match other URL rules, it will match this default policy. If the default policy is deleted, the access request for the domain name will be discarded when it does not match other rules and a 404 prompt will be returned. But you can still choose to delete the default policy, or manually add the default policy.

Did the above content solve your problem? Yes No