Just to confirm: disabling http2 in the standalone xml did fix the issue
We were also able to do this with a running instance using the jboss cli.
Thanks to Dmitry T. for the help!
On Wed, 19 Dec 2018, 14:02 Gareth Western <gareth.western+listman(a)gmail.com
It looks like the wildfly server used for the Keycloak 4.6.0.Final
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?