maintain support http2 sometime is nightmare, so remove it from core.
discus about it on
Conscrypt already support 64x. so you don’t neet to remove it
http2 for speed up and save connect. for detail pleaes google
in case you still want to wipe out Conscrypt and can’t do by yourself, can contact me at email@example.com
that kind of this discus (question, advice,..) should use google group
https://groups.google.com/forum/#!msg/idempiere than ticket
1.) Conscrypt does not support ppc64 or ppc64el. It only supports i386, amd64, ARM, and MIPS. This is a Google business decision at the moment and is one reason why, in my opinion, Conscrypt needs to remain optional – Conscrypt is not a community developed library, and if Google doesn't want something it simply doesn't happen.
3.) I'm more than happy to update the documentation once I understand the process to use http2 instead of Conscrypt. There is nothing online about switching?
I think in past we have discussed about this. If I recall correctly, our conclusion was something like:
The default recommended method to use iDempiere is via a proxy (f.e. apache or nginx) - and in this case the http/2 must be managed by those, so, in the recommended method conscrypt is not required, no need to push it by default. We can keep conscrypt available in case somebody wants to use it, I guess it would just be a matter of editing the jetty-ssl-context.xml to enable it, but there is no need to make it default.
The scenario at this moment is not critical anyways, conscrypt is enabled by default, but can be easily disabled editing the jetty-ssl-context.xml
I’ve been looking for documentation on how exactly to use iDempiere without Conscrypt, but have not been able to find it. Editing the XML is not trivial without some idea of what the end goal for configuration is.
Should I open a new report on the missing documentation?