Currently undertow provides read, write, and idle timeouts, which apply to all operations in ways that can unexpectedly cause issues, for example a read timeout can cause websockets to fail when it's meant to defensively stop servlet requests from holding worker threads longer than necessary.
A filter or handler to interrupt long-running operations can leave the connection in an undesirable state, and isn't guaranteed to close the connection.
A preferable and less dangerous solution is to provide an API to set timeouts which apply to blocking reads and writes on interactions with a BlockingHttpExchange.

Thoughts?