Are you using the latest Java 8 runtime? Http2 clients will reject old ciphers (Java 7)
and that version of the alpn hack is only compatible with Java 8 releases after January.
A self signed cert should be fine as long as you add the exception in the browser.
Sent from my iPhone
On May 27, 2015, at 8:43 PM, Michael Hixson
I'm trying to test out HTTP/2 with undertow-core 1.2.6.Final. I
haven't been able to see any HTTP/2 traffic to from my server locally,
and I'm not sure what I'm doing wrong.
I mostly followed the example code here:
- Enable the HTTP2 and SPDY server options on my Undertow builder.
- Am using an HTTPS listener with an SSLContext.
- Have a maven dependency for org.mortbay.jetty.alpn:alpn-boot:8.1.3v20150130.
But when I make requests in a browser (tried Chrome and Firefox), it
says the protocol for all my requests is HTTP/1.1. I know at least
Chrome supports HTTP2 because I can see it using HTTP2 in that very
same browser console - other resources loaded by that same page on my
website (e.g. to Google Analytics) are delivered *not* over HTTP/1.1.
Has anyone been able to use HTTP/2 with Undertow on localhost
successfully? Any ideas what I might be doing wrong?
I'm using a self-signed certificate, if that matters. I also tried
the keystores in the examples directory on Github and got the same
result. Thinking something else in my app was interfering with this,
I also tried a root HttpHandler that simply wrote "hello" to the
output stream for every response. No success there either.
My apologies if this is me not understanding HTTP/2 rather than any
undertow-dev mailing list