Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000Asegn project_key: JBPAPP6 Support configuring a connector on the http socket and then redirect to the https socket without having to specify the actual port number outside of the socket-binding-group. The referenced forum thread has an example that uses "redirect-port" for this, but a new attribute would be needed, since changing the meaning of "redirect-port" would be incompatible.
Link: Added: This issue relates to AS7-4295
Linked is the bug logged for AS7, this one is to track this issue being reported by a customer in EAP 6.
Docs QE Status: Removed: NEW
Property substitution like 'redirect-port="${jb.redirect.port:8180}"' can be a workaround but of course unifying in socket-binding is smarter.
PR: https://github.com/jbossas/jboss-eap/pull/1028 Upstream : https://github.com/wildfly/wildfly/pull/6011
Verified with EAP 6.3.0.ER1. I have verified that using redirect-binding attribute of the connector, I am able to define the redirection using socket binding and that redirect-port can still be used for directly defining redirect port using a port number. This functionality needs to be documented, I have created BZ#1089361 for it.