– URLs or patterns occurring in URLs

– Values of web page content

– Values of web page properties

– URL applications are imported as Advanced Web applications, not URL applications. The server information for the URL applications is preserved in the import.

– Applications are imported as High Priority applications. AppResponse 11 supports up to 600 High Priority applications, If you have more than 600 applications, create two .csv files, one (FILE A.csv) with no more than 600 High Priority applications, the second (FILE B.csv)with the remaining applications. Import FILE B.csv first and then edit the applications to change each to Medium or Low Priority applications. Next, import FILEA.csv.

– AppResponse 11 application names are case-sensitive and must be unique. The names of the imported AppResponse 9.6.x applications cannot duplicate the name of existing AppResponse 11 applications. An error message with the list of duplicate names is displayed when duplicates are found during an import. Those application names must be changed in the .csv file before they can be imported.

Conflicts with AppResponse 11 Auto-Recognized applications may occur. For example, these default applications in AppResponse 9.6.x will have conflicting names during import: DNS, HTTP, ICMP, IMAP, POP3, RTCP, SMTP, and SSH. These applications can be imported by changing their names to all lowercase in the .csv file.

– When imported, an AppResponse 9.6.x Auto-Recognized application is replaced by the corresponding AppResponse 11 Auto-Recognized application.

– General applications can be any combination of user-supplied ports, protocols, server IP addresses, and Auto-Recognized applications.

– High Priority applications are matched to all incoming traffic. If traffic, for example, an individual TCP connection, matches more than one General application it contributes metrics to all those applications.

– Performance data that ASA records for these applications are not affected by topping, that is, metrics for all General applications with high priority that were seen in a minute are recorded in the AppResponse 11 performance database.

– These General applications also can be any combination of user-supplied ports, protocols, server IP addresses, and Auto-Recognized applications.

– These medium priority applications are matched to all incoming traffic. If traffic matches more than one General application with this priority setting it contributes metrics to all those applications.

– Performance data that ASA recorded could be affected by topping - this is why this is a lower priority than High.

– Users also can create General applications with Traffic Matching Mode set to Low Priority. AppResponse 11 prevents these General applications from using any Auto-Recognized application definitions. Instead, these General applications only use combinations of user-supplied port, protocols and server IP addresses.

– These applications will be matched against traffic that did not match any applications in steps 1), 2), and 3) above. These could be considered user-defined applications.

– Performance data that ASA recorded could be affected by topping.

– Traffic that did not match any applications in steps 1) through 4) above is matched against Port Alias definitions. A user can modify port alias definitions or create new definitions of their own at Definitions > Port Aliases. Performance data that ASA recorded could be affected by topping.

– References to properties in the table above by using a dollar variable.
For example: $url

– A match against a regular expression by using the “in” operator with the regex contained in quotes.
For example: $url in "pattern"

– A match against an IP address by using the “in” operator with the address in CIDR format.
For example: $serverIP in 192.168.1.0/24

– Numerical comparisons: <, <=, >, >=, =, <>, !=
For example: $packetsIn > 2

– Boolean logic: and, or, not
For example: $url in "pattern1" or $url in "pattern2" or not $url in "pattern3"

– Grouping (by using parenthesis).
For example: $url in "pattern" and ($serverIP in 192.168.1.0/24 or $pageTime > 5.0)

– Check against a set of values with the “in” operator and {{ }} as delimiters.
For example: $responseCode in {{ 404, 501, 502 }}