<@U092308M7> You might remember the problem I've h...

# ktor

[Sergey Chikin]

@orangy You might remember the problem I've had with exceptions being on the log while response was being generated correctly. I did a little debugging on that. It seems like the problem is that request processing pipeline is ran inside the coroutine and when that coroutine is finishing it's raising CancellationException upon successful completion. The exception is getting caught by the defaultEnginePipeline that's trying to respond with HTTP500 because it caught the exception