Lachlan

It didn't stackoverflow for me after a few minutes but didn't seem to be progressing at all. I guess it probably would have stackoverflowed if it was left running for...

@paplorinc Yes, I have been working on a PR for this, although it will probably not make 9.4.31. This is a general review of temporary buffer usage, can you provide...

@paplorinc PR #5045 should improve the temporary buffer usage for small binary messages. But we are still not reusing the buffers. We use `ByteArrayOutputStream` to aggregate the payloads of a...

> What if instead of that, we returned a blocking inputstream, which would fetch until isFin is true, reading from the underlying, read-only ByteBuffers? Take a look at [MessageInputStream](https://www.eclipse.org/jetty/javadoc/current/org/eclipse/jetty/websocket/common/message/MessageInputStream.html), this...

> While you're a it, I think there is a bug in ee9 ContextHandler.checkAlias: if the resource is an alias but there are no alias checks then false is returned...

@lorban currently the way to allow aliases like this is to add the `AllowedResourceAliasChecker`. I tried this with this test and it passes if the `AllowedResourceAliasChecker` is added to the...

PR #8449 has been merged so I think this can be closed. As a summary, the same AliasCheck class is now used for jetty-core, ee10 and ee9. Multiple `AliasCheck`s can...

@janbartel thoughts?

@minduch can you try setting your alpn default protocol to `HTTP/1.1`. WebSocket upgrade comes as an HTTP/1.1 request, with the exception of RFC8441 where a single HTTP/2 stream is upgraded...

Jetty 10+ does support the HTTP/2 WebSocket upgrade, but it is a CONNECT request and only upgrades a single HTTP/2 stream not the entire connection. Jetty does not support WebSocket...