- All Superinterfaces:
Rule
- Functional Interface:
- This is a functional interface and can therefore be used as the assignment target for a lambda expression or method reference.
servlet requests
.
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 non-terminating
actions
.
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?
-
Nested Class Summary
-
Method Summary
Modifier and TypeMethodDescriptionperform
(FirewallContext context, HttpServletRequest request) Checks if the given request is matched.
-
Method Details
-
perform
Matcher.Result perform(FirewallContext context, HttpServletRequest request) throws IOException, ServletException Checks if the given request is matched. This must not have any side-effects on the context, request, or response.- Parameters:
context
- The current firewall contextrequest
- The request being matched- Returns:
- Returns
Matcher.Result.TERMINATE
propagated from when a nested terminal action is performed,Matcher.Result.MATCH
when the rule matches but no nested terminal action is performed (non-terminal might have been performed), orMatcher.Result.NO_MATCH
when the rule is not matched (nested non-terminal actions might still have been performed, depending on matcher implementation). - Throws:
IOException
ServletException
-