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
An exception raised in the lifecycle (but not handler) of a request on an ASGI-served application should be able to pass a status code.
In my experiment, raising a BadRequest in asgi.py will cause the ASGI server return 500 error, instead of 400. This seems out of the scope of this PR, but I am wondering whether we should change the raised error to ServerError or others before we figure out how to let ASGI server return a 400 error.
An exception raised in the lifecycle (but not handler) of a request on an ASGI-served application should be able to pass a status code.
Originally posted by @ChihweiLHBird in #2606 (comment)
The text was updated successfully, but these errors were encountered: