Documentation

The result of matching against a path in the route tree.

A Delayed without any stored checks.

Fail with the option to recover.

Fail fatally, i.e., without any option to recover.

Gain access to the incoming request.

Add a capture to the end of the capture block.

Add a parameter check to the end of the params block

Add a header check to the end of the headers block

Add a method check to the end of the method block.

Add an auth check to the end of the auth block.

Add a content type and body checks around parameter checks.

We'll report failed content type check (415), before trying to parse query parameters (400). Which, in turn, happens before request body parsing.

Add an accept header check before handling parameters. In principle, we'd like to take a bad body (400) response take precedence over a failed accept check (406). BUT to allow streaming the body, we cannot run the body check and then still backtrack. We therefore do the accept check before the body check, when we can still backtrack. There are other solutions to this, but they'd be more complicated (such as delaying the body check further so that it can still be run in a situation where we'd otherwise report 406).

Many combinators extract information that is passed to the handler without the possibility of failure. In such a case, passToServer can be used.

Run a delayed server. Performs all scheduled operations in order, and passes the results from the capture and body blocks on to the actual handler.

This should only be called once per request; otherwise the guarantees about effect and HTTP error ordering break down.