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

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 should the LTM Specialist do to resolve this?

Answer options

• A. Use the followinG. switch -lc [HTTP::uri]
• B. Use the followinG. switch [string tolower [HTTP::uri]]
• C. Set the "Case Sensitivity" option of each member to "None".
• D. Select the "Process Case-Insensitivity" option for the virtual server.

Correct answer: B

Explanation

The correct answer is B because applying the 'tolower' function ensures that the URI is compared in a case-insensitive manner. Option A is incorrect as the '-lc' switch does not exist in this context. Option C would not resolve the issue at the iRule level, and option D is not the appropriate solution as it pertains to the virtual server settings rather than the iRule behavior.