Greg Wilkins

@joakime I'm inclined to close this one. I do not think there is a problem here.

This is not an issue we need to fix. Closing.

If you can reproduce on jetty 12, then can obtain a dump of both the JVM stacks and the jetty client (I assume it is the client you are reporting...

@lachlan-roberts is this something you'd like to look into?

I agree this is not an issue. Closing!

@c0nrad webtide.com:443 is up now. If you have a distribution of jetty-9.3.x, the you can easily run a http2 server: ``` mkdir test cd test java -jar $JETTY_HOME/start.jar --add-to-startd=http,https,http2,http2c,deploy java...

@c0nrad I ran exactly that command and the result is that every fuzzer gives up with "sever[sic] doesn't support http2" ``` gregw@Tile440: ~/src/http2fuzz (master) [2002] ./http2fuzz --target webtide.com:443 2015/12/02 10:52:28...

Potentially a `docker cp` command could be used to extract the webdefault.xml from the target image. Potentially it could extract the jetty distribution as well.

So we need to work out how to publish a webdefaults.xml that the SDK can choose based on the deployment target. The URL to the master version of it is...

Hmmm I'm not a huge fan of JNDI... it is really rather over complex for a map of map of map... of strings. In jetty generally we have gone away...