How Requests for Web Resources are Evaluated

Because Web resources can be defined quite broadly, the appliance follows a rule for determining which Web application profile to apply to an incoming request: it chooses the profile associated with the most specific resource.

For example, suppose you’ve defined these two resources:

• A DNS domain (xyz.com) with Web application profile A attached

• A specific Web server (web1.xyz.com) with Web application profile B attached

If a user request comes in for https://web1.xyz.com/timesheet.html, the appliance uses Web application profile B because it is associated with a more specific resource (the Web server) than Web application profile A (the domain). The actual order that the appliance uses is as follows:

URL —> Host name —> IP address —> Subnet/IP range —> DNS domain