pl.iterators.stir.server

Rejection created by the various pl.iterators.stir.server.directives.SecurityDirectives. Signals that the request was rejected because the user could not be authenticated. The reason for the rejection is specified in the cause.

Rejection created by the 'authorize' directive. Signals that the request was rejected because the user is not authorized.

Collects all default directives into one trait for simple importing.

Collects all default directives into one object for simple importing.

Rejection created by unmarshallers. Signals that the request was rejected because the requests content-type is unsupported.

Rejection created by parameter filters. Signals that the request was rejected because a query parameter value was not equal to required one.

Rejection created by form field filters. Signals that the request was rejected because a form field could not be interpreted.

Rejection created by header directives. Signals that the request was rejected because a header value is malformed.

Rejection created by parameter filters. Signals that the request was rejected because a query parameter could not be interpreted.

Rejection created by unmarshallers. Signals that the request was rejected because unmarshalling failed with an error that wasn't an IllegalArgumentException. Usually that means that the request content was not of the expected format. Note that semantic issues with the request content (e.g. because some parameter was out of range) will usually trigger a ValidationRejection instead.

Rejection created by method filters. Signals that the request was rejected because the HTTP method is unsupported.

Rejection created by the cookie directive. Signals that the request was rejected because a cookie was not found.

Rejection created by form field filters. Signals that the request was rejected because a form field was not found.

Rejection created by header directives. Signals that the request was rejected because a required header could not be found.

Rejection created by parameter filters. Signals that the request was rejected because a query parameter was not found.

A PathMatcher tries to match a prefix of a given string and returns either a PathMatcher.Matched instance if matched, otherwise PathMatcher.Unmatched.

Rejection created by scheme filters. Signals that the request was rejected because the Uri scheme is unsupported.

A Route that can be implicitly converted into a Directive (fitting any signature).

A special Rejection that serves as a container for a transformation function on rejections. It is used by some directives to "cancel" rejections that are added by later directives of a similar type.

Consider this route structure for example:

   put { reject(ValidationRejection("no") } ~ get { ... }

If this structure is applied to a PUT request the list of rejections coming back contains three elements:

1. A ValidationRejection
2. A MethodRejection
3. A TransformationRejection holding a function filtering out the MethodRejection

so that in the end the RejectionHandler will only see one rejection (the ValidationRejection), because the MethodRejection added by the get directive is canceled by the put directive (since the HTTP method did indeed match eventually).

Rejection created by the validation directive as well as for IllegalArgumentExceptions thrown by domain model constructors (e.g. via require). It signals that an expected value was semantically invalid.