This article contains information about advanced policy engine operators' case sensitivity on a NetScaler appliance.

Background

NetScaler software contains two policy engines – advanced and classic. You can only use the advanced policy engine to create expressions for the Responder policies. When implementing a Responder policy by creating an expression that uses the "contains" operator, you might notice that the results are case sensitive.

Advanced Policy Engine Operators' Case Sensitivity on a NetScaler Appliance

At times, you might need an operator to be case insensitive, such as specifying a URL in a Responder policy. This is because you might not want to terminate a client request based on the case of the characters used in the URL. However, when you use an operator in an advanced policy engine, it is case sensitive. The following is an example of an expression that is case sensitive:
HTTP.REQ.URL.CONTAINS("home")

When you need to create an expression that must not be case sensitive, you need should use another operator, SET_TEXT_MODE(IGNORECASE), to ensure that the result of the expression is not case sensitive. The following is an example to ensure that the previous expression is not case sensitive:
HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS("/home")

Note: When using the classic policy engine in the various features of the NetScaler appliance, the "contains" operator is not case sensitive.