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)
jetty-websocket-httpclient.xml
should be in your classpath, it is to load a specific HttpClient configuration for JSR356 users (useful for proxy configurations, specific security configurations, specific ssl/tls configurations, etc)
maven-jetty-plugin
then you are using the old plugin.
jetty-maven-plugin
Failed to upgrade to websocket: Unexpected HTTP Response Status Code: 0 null
indicates both an old Jetty version in use (the message has been cleaned up in recent versions), and an HTTP response from the remote that isn't a WebSocket upgrade. (details of the failure are typically reported in logging)
proxy
module in your ${jetty.base}