Use this page to associate routing policy HTTP rules with on demand routers (ODRs) and ODR clusters.
To view this administrative console page for ODRs, click
.To view this administrative console page for ODR clusters, click
.To modify rules with the rule builder, you must have administrator or configurator administrative privileges.
Builds a new rule.
Deletes a rule.
Prioritizes the rules in the case of multiple rules. The order of rules is key in determining matches. If a match occurs on the first rule, subsequent rules are not pursued.
Actions refer to the incoming HTTP request.
Specifies cluster, server, module.
Specifies cell.
The multi-cluster routing policy field is displayed when you select any of the permit actions. Also, the field only applies if there are multiple target clusters. If the target clusters are dynamically computed, the number and order of target clusters is not known until runtime.
This field is displayed when you select the redirect action. With this routing policy, the ODR redirects the request to the specified URL.
This field is displayed when you select the reject action. This routing policy causes the ODR to reject the request, and return the specified HTTP error code.
This field is displayed when you select the local resource action. With this routing policy, the request is routed to the local file system of the ODR from which static content is served.
Commits your new rule settings.