tree 15cc78e9d573d2b99f082c3a367698057692fccb
parent 2342590d94f432b5fee3d4428ade6a386f725d3b
author Edwin Kempin <ekempin@google.com> 1575549304 +0100
committer Edwin Kempin <ekempin@google.com> 1575562289 +0100

ExceptionHook: Add method that allows to control the status code of the response

If during the execution of a REST request an exception occurs we return
a 500 Internal Server Error response to the user, unless the exception
is sepcifically caught and handled in RestApiServlet.

Now, with the new method implementors of the ExceptionHook extension
point can control the REST response for arbitrary exceptions. The new
getStatusCode method allows them to decide on the HTTP status code and
the already existing getUserMessage method allows them to define the
message in the response body.

This is useful if environment-specific exceptions should be handled.
E.g. at Google we have a specific exception that is thrown if a client
disconnects. At the moment this exception results in an internal server
error, which affects our SLO metrics. A disconnected client is not an
error and we would rather return 200 OK in this case.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I04b1e2cfc002289ca8b405ce11449d3c445165c5