[net] Expose Jetty EndPoint in http requests

[GiviMAD]

Hello, I would like to merge these small workaround that allows to access the underling Jetty EndPoint when using an http client created using the WebClientFactory.

It mimics the way the EndPoint is exposed in recent Jetty versions so it will become useless in case of an update.

I need it in order to proxy the socket data for upgraded WebSocket connections through the OpenHAB Cloud Connector.

[GiviMAD]

Hello @J-N-K, would you able to give your opinion on whetter is it good to merge this change or if it will be better to upgrade the Jetty client to a more recent version where the EndPoint is already exposed?

Jetty 9 is quite old but still listed as stable here https://eclipse.dev/jetty/download.php#version-table.

I needed it for the cloud connector PR openhab/openhab-addons#16403 to proxy the socket data between the cloud and the connector though the Socket.IO connection. I chosed that solution to avoid the parsing of the websocket frames in the cloud, as the cloud is shared by many clients I think this way is the less resource intensive.

[wborn]

whetter is it good to merge this change or if it will be better to upgrade the Jetty client to a more recent version where the EndPoint is already exposed?

The Jetty upgrade depends on Apache Karaf upgrading to a recent Pax Web version, see #3315. So until that becomes available the workaround makes sense.

[wborn]

Thanks for working on improving the WebSockets API compatibility!

[GiviMAD]

Thank you for the review!