@jaen: what version of openssl are you using?

@jcrossley3:

╰─$ openssl version
OpenSSL 1.0.2d 9 Jul 2015

That said, browser can't connect either

@jaen: i have things connecting via ssl using undertow's key/trust stores, but i don't see the http2 request headers in either FF or chrome

@jaen: i'm using an older openssl, which may be my problem. let me push my changes and have you try.

Hmm, you say you're using key/trust stores (I assume directly). Maybe less-awful-ssl is setting it up from the keys wrong?

mayhap. i tried creating my own and failed with the same errors i was getting with your creds.

there are a lot of moving parts here, including jvm and openssl versions

Right. I hoped it could just work™ and was kinda stumped, even though I tried to follow the less-awful-ssl readme you linked to as a way to set that up. Is there any alternative you suggest? Say, creating those key/trust stores you speak of (I don't really know what they are, in Ruby you just dealt with plain ceritifcate files)

@jaen: PR sent

Interesting

Openssl connects properly

But browser says no data is sent

Non-ssl port works properly

Is the behaviour the same for you?

Oh, curl works. Interesting, so it's just browser that complains.

https://localhost:8443 works in my browsers

Oh, it has to have the protocol, I used just localhost:8443

Though yeah, no HTTP2 enabled. Is the way I try to enable it proper, or is there something I'm missing?

Because that is all result of me source-diving, so I might have missed something with there not being documentation on how to enable it

(or at the very least I couldn't find it)

i'm not sure, tbh. need to research a bit more. i was hoping your openssl version would've been enough to do the trick, but i'm never that lucky.

I see. But if I understand correctly since SSL is working then there must be something else missing to enable HTTP2, right?

i think so, yeah

once we figure that out, we'll add an :http? option to encapsulate that

:http2?

for some reason, i didn't think undertow would require any config since http2 really should be driven by the browser

that's why we called it "experimental support" -- sorry for giving you the wrong impression there, but i appreciate you forcing us to fix it.

Sure, no problem

That's nothing really pressing though, since it's just a university project and I just wanted to be fancy.

I'll keep an eye on it and thanks for the help!

i can respect that

Ok, I have to run, thanks again!