Currently the support for websocket is realized using the Jetty-client which is per se fine and works as expected.
As we use htmlunit in a environment with Selenium and a embedded Jetty for serving our application we struggle with jar versions for our testenvironment. We already updated to Jetty 10 and alternatively use Jetty 11 to prove compatibility with JakartaEE 9.
As far as I can see htmlunit is more or less hardwired to using Jetty 9.x even if there seems to be the idea of plugging different websocket-implementations through WebSocketAdapter. Unfortunately there is no configuration to link a different implementation.
Introducing such a configuration would allow to use different client-implementations and possibly could as well help to scope with issues like #36
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too