Christopher Mindus

The following changes would probably do good in **Fingerprint.java**: ```java public boolean execute(String action, JSONArray args, CallbackContext callbackContext) { // Just making sure! if (callbackContext == null) { Log.v(TAG, "Fingerprint...

I wound't know why the `callbackContext` is null, but it would certainly avoid the `NullPointerExceptions`and be thread-safe.

To see our server in action using Jetty 11.0.8 WebSockets with Conscrypt and without HTTP/2 and HTTP/3, open a browser (e.g. Chrome) at [iizi Demo Server at mt.iizi.co](https://mt.iizi.co), then click...

Perhaps I need to be a little more specific: the WebSocket is configured with the code above, then referencing the Java class attached. The websocket is configured with the code...

Yes we know this works - i.e. that using only HTTP/1 and disabling HTTP/2 and HTTP/3 works with WebSockets. This, however, turns our Jetty-based server into an "OLD" HTTP/1.1 server...

I am reading about Chrome's support for WebSockets over HTTP/2. Then there are stuff written for Bootstrapping WebSockets with HTTP/2 and for Bootstrapping WebSockets with HTTP/3. Is there no way...

Couldn't the upgrade process for WebSocket look like somthing described below in order for WebSockets to be able to function in a HTTP/3, HTTP/2 and HTTP/1 environment with security enabled...

@lachlan-roberts @joakime Just to be sure: calling `alpn.setDefaultProtocol(httpProtocol)`, where `httpProtocol` is the `String` returned by the `HttpConnectionFactory` will allow HTTP/3, HTTP/2 and HTTP/1.1 (perhaps also HTTP/1.0)? To be really clear,...

@lachlan-roberts @joakime When would Jetty support HTTP/2 (and/or 3 [I know 3 is "hardly RFC" yet]) WebSocket Bootstrapping? Will it be announced somewhere so I can keep track of it?

@lachlan-roberts @joakime Sorry: forgot some questions, what does the browsers or WebViews request as default protocol below: 1. Chrome? 2. MS IE 11? 3. MS Edge? 4. macOS/iOS Safari? Please...