metabase.middleware.exceptions — metabase-core 1.0.0-SNAPSHOT

Ring middleware for handling Exceptions thrown in API request handler functions.

api-exception-response clj multimethod

(api-exception-response e)

Convert an exception from an API endpoint into an appropriate HTTP response.

catch-api-exceptions clj

(catch-api-exceptions handler)

Middleware that catches API Exceptions and returns them in our normal-style format rather than the Jetty 500 Stacktrace page, which is not so useful for our frontend.

catch-uncaught-exceptions clj

(catch-uncaught-exceptions handler)

Middleware that catches any unexpected Exceptions that reroutes them thru raise where they can be handled appropriately.

genericize-exceptions clj

(genericize-exceptions handler)

Catch any exceptions thrown in the request handler body and rethrow a generic 400 exception instead. This minimizes information available to bad actors when exceptions occur on public endpoints.

message-only-exceptions clj

(message-only-exceptions handler)

Catch any exceptions thrown in the request handler body and rethrow a 400 exception that only has the message from the original instead (i.e., don't rethrow the original stacktrace). This reduces the information available to bad actors but still provides some information that will prove useful in debugging errors.