immutant

http://immutant.org Note: dev discussion happens in #immutant on FreeNode IRC.
2015-11-18T13:38:37.000031Z

@jaen: what version of openssl are you using?

jaen 2015-11-18T13:45:01.000032Z

@jcrossley3:

╰─$ openssl version
OpenSSL 1.0.2d 9 Jul 2015

jaen 2015-11-18T13:45:08.000033Z

That said, browser can't connect either

2015-11-18T13:49:16.000034Z

@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

2015-11-18T13:50:00.000035Z

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

jaen 2015-11-18T13:50:58.000036Z

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

2015-11-18T13:52:47.000037Z

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

2015-11-18T13:53:16.000038Z

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

jaen 2015-11-18T13:55:21.000039Z

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)

2015-11-18T13:56:45.000040Z

@jaen: PR sent

jaen 2015-11-18T14:02:11.000041Z

Interesting

jaen 2015-11-18T14:02:16.000042Z

Openssl connects properly

jaen 2015-11-18T14:02:22.000043Z

But browser says no data is sent

jaen 2015-11-18T14:03:00.000044Z

Non-ssl port works properly

jaen 2015-11-18T14:04:13.000045Z

Is the behaviour the same for you?

jaen 2015-11-18T14:04:50.000046Z

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

2015-11-18T14:05:09.000047Z

https://localhost:8443 works in my browsers

jaen 2015-11-18T14:05:52.000048Z

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

jaen 2015-11-18T14:07:44.000049Z

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

jaen 2015-11-18T14:08:38.000050Z

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

jaen 2015-11-18T14:08:47.000051Z

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

2015-11-18T14:10:39.000052Z

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. :simple_smile:

jaen 2015-11-18T14:12:37.000053Z

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

2015-11-18T14:12:51.000054Z

i think so, yeah

2015-11-18T14:13:37.000055Z

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

2015-11-18T14:13:45.000056Z

:http2?

2015-11-18T14:14:31.000057Z

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

2015-11-18T14:15:21.000058Z

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. :simple_smile:

jaen 2015-11-18T14:15:33.000059Z

Sure, no problem

jaen 2015-11-18T14:16:04.000060Z

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

jaen 2015-11-18T14:16:15.000061Z

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

2015-11-18T14:16:17.000062Z

i can respect that :simple_smile:

jaen 2015-11-18T14:17:11.000063Z

Ok, I have to run, thanks again!