Filter mappings that reference a non-existent filter will not be applied.
Every filter mapping must correspond to a valid filter definition in order for it to be applied.
Example 1: The following example shows a filter mapping that references the non-existent filter AuthenticationFilter
. Because the definition is missing, the filter AuthenticationFilter
will not be applied to the designated URL pattern /secure/*
and might cause a runtime exception.
<filter>
<description>Compresses images to 64x64</description>
<filter-name>ImageFilter</filter-name>
<filter-class>com.ImageFilter</filter-class>
</filter>
<!-- AuthenticationFilter is not defined -->
<filter-mapping>
<filter-name>AuthenticationFilter</filter-name>
<url-pattern>/secure/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>ImageFilter</filter-name>
<servlet-name>ImageServlet</servlet-name>
</filter-mapping>
[1] Standards Mapping - OWASP Top 10 2010 - (OWASP 2010) A6 Security Misconfiguration
[2] Standards Mapping - OWASP Top 10 2004 - (OWASP 2004) A9 Application Denial of Service
[3] Standards Mapping - Security Technical Implementation Guide Version 3 - (STIG 3) APP6080 CAT II
[4] Standards Mapping - Common Weakness Enumeration - (CWE) CWE ID 730
[5] Sun Microsystems, Inc. Java Servlet Specification 2.4
[6] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 - (PCI 1.1) Requirement 6.5.9