Ludovic Orban

**Jetty version(s)** 12.0.x **Description** Fails with `org.eclipse.jetty.client.HttpClientTLSTest expected an empty collection but within 5 seconds.` See: https://jenkins.webtide.net/job/jetty.project/job/jetty-12.0.x/396/testReport/junit/org.eclipse.jetty.client/HttpClientTLSTest/testEncryptedOutputBufferRepoolingAfterNetworkFlushThrows_boolean__2_/

Jetty 12 : EE10 implement default servlet serving jetty-dir.css

5

Make ee10 `DefaultServlet` able to serve jetty-dir.css

The `LoadGenerator.Builder` currently lacks an easy way to set a `ByteBufferPool`, something like the following: ```java LoadGenerator.builder() .byteBufferPool(bufferPool) ... ``` Currently the only way to set the byte buffer pool...

WIP

Jetty 12: review `resolve()` and `getPath()` contracts in `ResourceCollection` and `MemoryResource`

2

**Jetty version(s)** 12 **Description** Review how `resolve()` and `getPath()` are supposed to behave when directory and non-directory resources are part of a `ResourceCollection`, and for `MemoryResource` in general. Or if...

**Jetty version(s)** 12 **Description** Here's the current state about which of the static content serving mechanisms (ee9 `DefaultServlet`, ee10 `DefaultServlet` and `ResourceHandler`) can serve jetty-dir.css: | | jetty-dir.css | |...

Jetty 12: `ContextHandler.getTempDirectory()` does not respect the `Context.getTempDirectory()` contract

5

The `Context.getTempDirectory()` contract states that null should never be returned, while the `ContextHandler.getTempDirectory()` implementation may return null depending on the `MultipartConfigElement`. This PR makes sure that `ContextHandler.getTempDirectory()` never returns null....

WIP See #10741

**Jetty version(s)** 12.0.x **Enhancement Description** Currently, when `WebSocketConnection.onIdleExpired` or `WebSocketConnection.onReadTimeout` is called, the user of the API has no way to handle the timeout. CometD would be a prime user...

Fix buffer leaks in FCGI and H3 `HttpClientIdleTimeoutTest`

7

`testClientIdleTimeout` and `testRequestIdleTimeout` leak a buffer because the handler's callback is never completed and they don't give the server a chance to reclaim its resources after idle timeout. Note: the...