Request conditions can be combined via combine(Object), matched to
a request via getMatchingCondition(HttpServletRequest), and compared
to each other via compareTo(Object, HttpServletRequest) to determine
which is a closer match for a given request.
| Modifier and Type | Method and Description |
|---|---|
| public T | Returns: a request condition instance that is the result of combining the two condition instances.the condition to combine with. other)Combine this condition with another such as conditions from a
type-level and method-level |
| public int | compareTo(T other, HttpServletRequest request)
Compare this condition to another condition in the context of a specific request. |
| public T | Returns: a condition instance in case of a match ornull otherwise.Check if the condition matches the request returning a potentially new instance created for the current request. |
| combine | back to summary |
|---|---|
| public T combine(T other) Combine this condition with another such as conditions from a
type-level and method-level
| |
| compareTo | back to summary |
|---|---|
| public int compareTo(T other, HttpServletRequest request) Compare this condition to another condition in the context of
a specific request. This method assumes both instances have
been obtained via | |
| getMatchingCondition | back to summary |
|---|---|
| public T getMatchingCondition(HttpServletRequest request) Check if the condition matches the request returning a potentially new instance created for the current request. For example a condition with multiple URL patterns may return a new instance only with those patterns that match the request. For CORS pre-flight requests, conditions should match to the would-be, actual request (e.g. URL pattern, query parameters, and the HTTP method from the "Access-Control-Request-Method" header). If a condition cannot be matched to a pre-flight request it should return an instance with empty content thus not causing a failure to match.
| |