Interface Rejection
- All Superinterfaces:
Rejection
- All Known Subinterfaces:
CorsRejection,CustomRejection,RejectionWithOptionalCause
- All Known Implementing Classes:
AuthenticationFailedRejection,AuthorizationFailedRejection$,CircuitBreakerOpenRejection,CorsRejection,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
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
pekko.http.scaladsl.model.HttpResponses by the
handleRejections directive, if there was no way for the request to be completed.