Litestar
"Exception caught after response started" #4238
Replies: 1 comment 1 reply
-
|
Mhm. Are you using any custom middleware? This can happen if a middleware doesn't handle exceptions properly. If it raises an exception after it has started to send a response, this can happen, because then the internal exception handling middleware will catch that exception and try to send an error response. |
Beta Was this translation helpful? Give feedback.
-
|
I am using custom middleware, but I am not aware of any exceptions being raised by them, and I did ask if it was correct. See: https://github.com/orgs/litestar-org/discussions/3616 I am also subclassing the prometheus middleware and overriding e.g. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When our application gets lots of traffic, we sometimes see, e.g., this in the log:
We are using middleware and exception handling etc. I am trying to create an MCVE but it is not going great.
The client has a timeout, so I think this is related to the client disconnecting mid-response or something like that.
Is this to be expected or should some action be taken?
Beta Was this translation helpful? Give feedback.
All reactions