A serious error was discovered in the implementation of this feature, as disclosed in an advisory. The
ignoreCase attribute was implemented in reverse by mistake, and so the default value of "true" actually causes case-sensitive matching, generally not the intended result. Pending the release of V2.6.0 in the summer of 2016, most deployers will want to include
ignoreCase="false" when using this feature, along with a comment to revisit it once 2.6.0 is released, at which time a new setting with the proper implementation will be provided. In the V2.6 release the new
caseSensitive attribute, with a default of truefalse, controls the case sensitivity.