F5 BIG-IP LTM Specialist: Maintain and Troubleshoot — Question 78

A virtual server for a set of web services is constructed on an LTM device. The LTM Specialist has created an iRule and applied this iRule to the virtual server: when HTTP_REQUEST { switch [HTTP::uri] {
"/WS1/ws.jsp" {
log local0. "[HTTP::uri]-Redirected to JSP Pool"
pool JSP
}
default { log local0. "[HTTP::uri]-Redirected to Non-JSP Pool" pool NonJSP
}
}
}
However, the iRule is NOT behaving as expected. Below is a snapshot of the log:
/WS1/ws.jsp-Redirected to JSP Pool
/WS1/ws.jsp-Redirected to JSP Pool
/WS1/ws.jsp-Redirected to JSP Pool
/WS1/WS.jsp-Redirected to Non-JSP Pool
/ws1/WS.jsp-Redirected to Non-JSP Pool
/WS1/ws.jsp-Redirected to JSP Pool
/ws1/ws.jsp-Redirected to Non-JSP Pool
What is the problem?

Answer options

• A. The condition in the iRule is case sensitive.
• B. The 'switch' command in the iRule has been used incorrectly.
• C. The pool members of both pools need to be set up as case-insensitive members.
• D. The "Process Case-Insensitivity" option for the virtual server needs to be selected.

Correct answer: A

Explanation

The correct answer is A because the iRule's matching conditions are case sensitive, causing it to treat URIs with different cases as distinct. Other options do not address the core issue of case sensitivity in the URI checks performed by the iRule.