Runwar has supported HTTP2 for a while, but it seems it's off by default and we don't have a first class setting to turn it on.
Right now, If you want to enable it you can run the following command:
which puts the following in your server.json
Find a good place in the server.json for a dedicated setting. I'm not sure we can force it to be enabled by default since it seems to require SSL to also be enabled.
HTTP2 is enabled by default. I’ve removed the need for the extra proxy port which seemed to be incorrect in the first place as well as the SSL requirement since that’s part of the spec. It’s just that browsers won't actually use it unless you’re on HTTPS. You can turn off HTTP2 like so
Sami Hoda March 14, 2020 at 6:00 PM
There are a couple issues:
Enabling http2, requires SSL. If not SSL params are passed, then the server generates it own certs, which is not good (the browser displays an alert)
On OpenJDK11, with or without SSL params (since SSL is enabled for http2), it seems all SSL calls from CFML code fail with a handshake error. This one I am diagnosing further. From what I have read, openJDK10 changed a lot with certs, so something CBOX may be doing on openjdk may be causing an issue. Again, looking into this more.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Runwar has supported HTTP2 for a while, but it seems it's off by default and we don't have a first class setting to turn it on.
Right now, If you want to enable it you can run the following command:
which puts the following in your server.json
Find a good place in the server.json for a dedicated setting. I'm not sure we can force it to be enabled by default since it seems to require SSL to also be enabled.