In the following configuration, a virtual server has the following HTTP class configuration: HTTP Class 2 = No filters

Class 1 has specific filter criteria defined, so only requests that satisfy those criteria would match Class 1; unmatched requests continue to the next class.

An HTTP class with 'No filters' has no defined matching criteria, which causes it to match all HTTP requests by default, functioning as a wildcard or default class. When traffic is evaluated against the ordered list of HTTP classes, requests that do not satisfy the specific filter criteria of Class 1 fall through to Class 2. Because Class 2 has no filters, it accepts any remaining request, making it the effective matching class for those requests.

A request can only be matched by one HTTP class at a time; once it matches Class 2, it is not simultaneously matched by Class 1.

The request is not dropped because a class with no filters serves as a default match, ensuring the request is handled rather than discarded.