sbordet on jetty-10.0.x-1350-dynamic_client_transport
Issue #1350 - Dynamic selection… (compare)
sbordet on jetty-10.0.x-132_client_connector
sbordet on jetty-10.0.x
Issue #132 - ClientConnector ab… Issue #132 - ClientConnector ab… Issue #132 - ClientConnector ab… and 2 more (compare)
sbordet on jetty-9.4.x-3311-http_https_same_port
Fixes #3311 - Ability to serve … (compare)
org.eclipse.jetty.*is no different.
ConfigurableSpnegoLoginService.java:181may suffer from http://cwe.mitre.org/data/definitions/384.html. Just wanted to check if this may be a concern or if it's a false positive scan?
org.eclipse.jetty.websocket.servlet.WebSocketServlet, which doesn't seem to have access to the session
I've implemented the Jetty HTTP client logging approach which is described here: https://www.baeldung.com/spring-log-webclient-calls
But spring-cloud-sleuth has no instrumentation support for the Jetty HTTP client
Do you have any suggestions on how to implement Jetty HTTP client support with distributed tracing with sleuth?