A virtual server at 10.10.1.100:80 has the rule listed below applied. when HTTP_REQUEST { if {[HTTP::uri] ends_with "htm" } { pool pool1 } elseif {[HTTP::uri] ends_with "xt" } { pool pool2 } If a

pool1 is only selected when the URI ends with 'htm'; a URI ending in 'xt' does not satisfy that first condition and therefore bypasses pool1.

The second condition in the iRule checks whether the HTTP URI ends with the string 'xt'. A URI such as 'document.txt' satisfies this condition because the last two characters are 'xt', causing the LTM to direct the request to pool2.

The request is not dropped because the second elseif condition matches a URI ending in 'xt' and provides an explicit pool assignment, so the connection is forwarded normally.

The pool can be determined from the iRule logic - the 'xt' suffix match in the elseif branch unambiguously selects pool2 for the described request.