Interface Rejection

All Superinterfaces:
Rejection
All Known Subinterfaces:
CustomRejection, RejectionWithOptionalCause
All Known Implementing Classes:
AuthenticationFailedRejection, AuthorizationFailedRejection$, CircuitBreakerOpenRejection, ExpectedWebSocketRequestRejection$, InvalidOriginRejection, InvalidRequiredValueForQueryParamRejection, MalformedFormFieldRejection, MalformedHeaderRejection, MalformedQueryParamRejection, MalformedRequestContentRejection, MethodRejection, MissingAttributeRejection, MissingCookieRejection, MissingFormFieldRejection, MissingHeaderRejection, MissingQueryParamRejection, PathDirectives.TrailingRetryRejection$, RequestEntityExpectedRejection$, SchemeRejection, TooManyRangesRejection, TransformationRejection, UnacceptedResponseContentTypeRejection, UnacceptedResponseEncodingRejection, UnsatisfiableRangeRejection, UnsupportedRequestContentTypeRejection, UnsupportedRequestEncodingRejection, UnsupportedWebSocketSubprotocolRejection, ValidationRejection

public interface Rejection extends Rejection
A rejection encapsulates a specific reason why a Route was not able to handle a request. Rejections are gathered up over the course of a Route evaluation and finally converted to HttpResponses by the handleRejections directive, if there was no way for the request to be completed.