You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is related to Enterprise Gateway Issue 296. With the current implementation of JSONErrorsMixin.write_error() it is not possible to do the following:
Return custom error text associated with a status code.
Return custom status codes.
By extending the set_status() method with a reason named argument, both of the above can happen.
The text was updated successfully, but these errors were encountered:
Without adding a named argument of `reason` to tornado's `set_status()`
method, messages associated with a thrown HTTPError will not be returned
to the caller. Instead, the reason corresponding to the built-in status
code is returned. In addition, because the reason argument is used,
enforcement of a built in status code is skipped, thereby allowing for
the optional use of non-builtin status codes.
Fixesjupyter-server#283
Without adding a named argument of `reason` to tornado's `set_status()`
method, messages associated with a thrown HTTPError will not be returned
to the caller. Instead, the reason corresponding to the built-in status
code is returned. In addition, because the reason argument is used,
enforcement of a built in status code is skipped, thereby allowing for
the optional use of non-builtin status codes.
Updated the TestableJSONErrorsHandler class to have a compatible signature
to Torado's `set_status()` method (to include the `reason` parameter).
Fixesjupyter-server#283
This is related to Enterprise Gateway Issue 296. With the current implementation of
JSONErrorsMixin.write_error()
it is not possible to do the following:By extending the
set_status()
method with areason
named argument, both of the above can happen.The text was updated successfully, but these errors were encountered: