<p><strong><span style="font-size:18px">How to configure forwarding by domain name and by URL at the same time?</span></strong></p> <p><strong>Requirements:</strong></p> <p>You have two domain names which are www.a.com and www.b.com. It is required that when accessing www.a.com/index.html, forward the request to the back-end pool1 for processing and the requests to accessing other xxx.html URLs forward to back-end pool2 for processing.</p> <p><strong>You can configure the forwarding as follows:</strong></p> <p>You need to configure the policy for the forwarding of domain name www.a.com and index.html URL to pool1.</p> <p>You also need to configure the policy for the forwarding of domain name www.a.com and index.html URLs to pool2, otherwise 404 response code will be returned if the domain name matched to www.a.com has no relevant policy to match.</p> <p><strong><span style="font-size:18px">What is the order in which URL forwarding strategy is judged?</span></strong></p> <p>1.&nbsp;First, the &quot;URL forwarding rule&quot; is judged. If the URL match the forwarding rule, then traffic will be forwarded to the back-end resource pool specified by the rule;</p> <p>2. If a &quot;URL forwarding rule&quot; is not matched and a server resource pool is specified on the listener, the traffic will be forwarded to the resource pool specified by the listener;</p> <p>3.&nbsp;If you do not specify a server resource pool on the listener, the URL forwarding rule cannot be configured.</p> <p><strong><span style="font-size:18px">How many forwarding rules can be added to each listener?</span></strong></p> <p>The number of forwarding rules which is limited to each listener is 10 (excluding default rules).</p> <p>You can only a maximum of 10 rules each time (including domain name rules and URL rules.)</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p>