Joakim Erdfelt

I'd like to come up with a solution that's lamda friendly :nerd_face:

@markt-asf Having the `SendResult.getSession()` seems like a good choice at first blush. Let me think about that approach. So you see a use that might look like this? ``` java...

If you are in WebSocket you are no longer in HTTP. In HTTP/1.1 you are upgraded out of HTTP. in HTTP/2 and HTTP/3 there's never an HTTP layer, it connects...

I don't know if this is a good thing to have in the spec/api. I could easily see someone wanting to know duration of ping/pong round trip as well. And...

Jetty has had no requests for auto-ping, but several for auto-pong-reply (which is implemented). There are serveral libraries built on top of the jakarta websocket spec that handle send ping...

Eclipse Jetty ran into this with SSL/TLS handshake_exceptions on OpenJDK 8u252 and OpenJDK 11.0.7 Circular Exception references are legitimate and even Java's own `Throwable.printStackTrace()` supports them properly. It sucks to...

The `RequestLog` has transitioned from being a traditional `Handler` in the Jetty sense, to being a specialized implementation that the `HttpChannel` uses. This was done to address many a bug...

@ChrisMacpherson-awin seeings as the Jetty `Slf4jRequestLog` is an implementation of the `AbstractNCSARequestLog` it it satisfying the NCSA output format correctly. Altering it with a customizable pattern would no longer make...

Note that Jetty 9.4.15+ has a CustomRequestLog that accepts formatting. Example usage (with slf4j) ``` java Slf4jRequestLogWriter slf4jRequestLogWriter = new Slf4jRequestLogWriter(); slf4jRequestLogWriter.setLoggerName("my.requestlog"); // the slf4j named logger to output to...

> * Full request/response headers (not just one header with specific name, but all). This probably doesn't work on HTTP/2 (or the upcoming HTTP/3), nor would presenting the header hierarchy...