raise exception to close connection without response (aka nginx 444)

[samuelcolvin]

Feature request

(or perhaps this already possible, but I can't find where it's documented?)

Would be useful occasionally to be able to close a connection without a response, roughly equivalent to nginx's 444 pseudo response.

I guess best implemented as another exception similar to HTTPInternalServerError except closing the connection instead of return 500.

eg. ServerCloseConnection.

Is this possible cleanly and if so would it be useful?

[webknjaz]

According to https://habr.com/post/415565/ this causes modern browsers to to a ton of RETRIES. So I'm not sure whether it's very useful nowadays.

wrt naming I'd probably go for ConnectionClosedWithoutResponse as per https://httpstatuses.com/444

[kxepal]

Today you can just raise asyncio.CancelledError from request handler to close connection without response. Do we need another one for this case? It named quite clean and it acts the same way as if client closes connection on their side before server returned any response.

[samuelcolvin]

Agree with both of you.

CancelledError should suffice, if someone wanted a different exception (eg. to tell error logging middleware that the server cancelled the response) they could just subclass CancelledError.

[lock]

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.