Details
-
Sub-task
-
Resolution: Done
-
Major
-
8.0.0.Alpha4
-
None
Description
There was another issue (WFLY-1924) when two WildFly server called each other through SSL/TLS. This is all done and its working. But during the discussion it came up that the configuration of the xnio endpoint in class org.wildfly.extension.undertow.HttpsListenerService.startListening is hardcoded. In other parts of the system I have the ability to define my own set of options for xnios OptionMap through CLI. Would it be a good idea to enhance the Http(s)ListenerService that the defaults are still there, but can be overwritten from the XML/CLI?
Because I can now configure the client side, I don't really need it in the undertow subsystem at the moment. But there my be other use cases where a configuration option in the above listener would be nice.