Simone Bordet

@iiliev2 would you be able to try #12542 and report back if it works for you?

Flushing after the response status is not great for performance, so I would advise against. You can flush after the response headers by overriding `onServerResponseHeaders(...)`.

Along with the fix for this issue, we should fix the overrides for `ClientConnector.addEventListener()` and same for `HTTP2Session`.

I'm looking into this.

What happens on the server: ``` http2's onReset() HttpChannelState.onFailure() => generates a Runnable Runnable invokes failure listener registered in ServletChannelState.startAsync() ServletChannelState.asyncError() ServletChannel.handle(), case ASYNC_ERROR, that just rethrows ServletChannel.handleException() => if...

Regarding writes, Jetty 12 EE10 behavior is the correct one. In Jetty 12 EE10, after 3 seconds the response is aborted and the `ServletChannel` recycled by a `CompletionListener` registered in...

@niloc132 can you try #12370 and report back if it fixed the problem for you?

@niloc132 just to be clear, I agree that upon receiving a RST_STREAM from the client, it must be notified to the server. Actually, this behavior is configurable via `HttpConfiguration.setNotifyRemoteAsyncErrors()` which...

@niloc132 can you please elaborate on your testing results? I ask because now we have an explicit test that verifies that `onError()` is called, so Jetty should behave like Tomcat...

The `ConnectionFactory` that drives the TLS handshake to the end for the ACME client challenge. ```java public class ACMETLS1ServerConnectionFactory extends AbstractConnectionFactory { public ACMETLS1ServerConnectionFactory() { super("acme-tls/1"); } @Override public Connection...