IMO this feature should be oriented to sysadmins not just developers. Is there really added value for developers to use HTTPS or HTTPS/2?

It should be easy for sysadmins to setup TLS/SSL with "production" quality, from the gereration of the CSR that has to be send to the CA to the generation of the keystore.

BTW... how is the performance of HTTPS using pure Java vs Apache for example? is this feature oriented for developers because for use in production is not recommended?


Ing. Jorge Solórzano

about.me/jorsol

On Fri, Jun 3, 2016 at 3:52 AM, Tomaž Cerar <tomaz.cerar@gmail.com> wrote:
This is completely off topic for this thread, there was one earlier about what should go into 10.x....

Anywho, issue you mention was already resolved and hibernate updated in master some time ago.
which means it will be in next release, whatever that release will be.

--
tomaz

On Thu, Jun 2, 2016 at 6:29 PM, Harold Campbell <hcamp@muerte.net> wrote:
On Thu, 2016-06-02 at 09:22 +1000, Stuart Douglas wrote:
> Hi All,
>
> I would like to propose that we add support for HTTP/2 out of the box
> in Wildfly 10.1.
>

This lowly user desperately wants a release containing the fix to WFLY-
6283 sooner rather than later. I'm sure other people have other pet
bugs awaiting release.

I have no opinion on HTTP/2 being added other than to ask that pent up
bug fixes be kept in mind.

--
Harold Campbell <hcamp@muerte.net>

Roses are red;
        Violets are blue.
I'm schizophrenic,
        And so am I.


_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev