It looks like the wildfly server used for the Keycloak 4.6.0.Final image is
configured to use HTTP2. Is there an easy way to disable this? I think it
might be the cause of some strange behaviour in Chrome, similar to as
described here:
https://issues.jboss.org/browse/KEYCLOAK-2656.
The related 'test http2' issue is pending for the Keycloak 5.x release, so
i assume Keycloak 4.x does not officially support HTTP2, is that correct?
Kind regards,
Gareth