Ludovic Orban

I've marked the EE9 ISE issues as solved (done in https://github.com/jetty/jetty.project/pull/13345)

I definitely don't like solution 3 as it comes with too many surprising behaviors. Now, between solutions 1 and 2, I'm not sure which ones is best. It feels like...

IMHO the `CompletableFuture` API is orthogonal to the main problem, so we should not distract ourselves too much with this side problem. That being said, I think the main problem...

I've just noticed some other complicating factor we must be careful about: a lot of places where an `Invocable` is passed to `demand()`, the `InvocationType` is pre-computed at the time...

I like `Promise` because: - this PR adds a `Blocker.Promise` so it's trivial to implement the blocking API with the async one - `Promise` is already part of our async...

IIRC when we discussed that subject months ago, you already suggested that leaving ee9 untouched might be preferable. In my view, ee9 is in maintenance mode: bugs will be fixed...

Ideally, this should never happen. If that does happen, you're probably navigating somewhere between the unclear parts of the standards and a bug of some sort, not necessarily in Jetty...

Are you using HTTP/1.1 or HTTP/2? Knowing exactly how you configured your `ResourceHandler` is going to be necessary to figure out what the problem might be. It's even better if...

I believe I managed to reproduce your problem. In a nutshell, the problem is that you are calling an async API (`staticResourceHandler.handle( coreRequest, coreResponse, Callback.NOOP )`) from a blocking one...

@jaroslawr Sorry for the delay getting back to you. Have you got any news about this issue? I checked the `GZIPContentDecoder` failure path, and there is no obvious way suppressed...