Clojurians Log v2

Bit of an advanced question. What's the best practice for handling exceptions when using async ring?

(try (respond ...) (catch Exception e (raise e)))

has a problem which I've just discovered: if respond throws (which I'm seeing in response to an EofException - the client has disconnected but the server is still writing). This then means you call raise and try to send a second response, which then throws a very loud exception. From what I've seen, exception handling middleware seems to swap to respond if they have a handler for an exception (e.g. maybe you want to turn a FooException into {:status 200}). But this double write in the case of EofException leads to another exception due to the fact the response is already committed. I don't want to update every exception handling middleware library (e.g. reitit) with EofException handling specifically. Although perhaps reitit should allow me to specify a way to "skip" a response for some exceptions and delegate back to the original raise. So it might be a slight tweak to how https://github.com/metosin/reitit/blob/310dcd0e9933237326d2648f19b23cbbd266de8b/modules/reitit-middleware/src/reitit/ring/middleware/exception.clj#L38-L42.