Base API for servlet-based application request filtering.
@FunctionalInterface public interface Matcher extends Rule
A matcher must not have any side-effects on the context, request, or response.
It may only have side-effects outside of the request processing, such as internal statistics on its own use.
Statistics providing rules, however, should be implemented as
It is possible for matchers to have nested rules (including both matchers and/or actions).
TODO: Include pathInfo in servletPath regarding path space lookups? TODO: matchers should be in own submodule? TODO: Is this redundant with https://docs.spring.io/spring-security/site/docs/4.2.5.RELEASE/apidocs/org/springframework/security/web/util/matcher/package-summary.html?
|Modifier and Type||Interface and Description|
Matcher.Result perform(FirewallContext context, HttpServletRequest request) throws IOException, ServletException
context- The current firewall context
request- The request being matched
Matcher.Result.TERMINATEpropagated from when a nested terminal action is performed,
Matcher.Result.MATCHwhen the rule matches but no nested terminal action is performed (non-terminal might have been performed), or
Matcher.Result.NO_MATCHwhen the rule is not matched (nested non-terminal actions might still have been performed, depending on matcher implementation).
Copyright © 2018–2020 AO Industries, Inc.. All rights reserved.