[
https://issues.jboss.org/browse/JBAS-9345?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-9345:
------------------------------------
There won't be any JBoss AS 5.x community release. So there won't be any backports
to community 5.x version. However, if you are using JBoss EAP (the paid version of the
application server), then it can be backported in that EAP 5.x series.
It seems impossible to redirect to the port that an external web
server listens on without deleting/disabling the SSL/TLS connector
-----------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-9345
URL:
https://issues.jboss.org/browse/JBAS-9345
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: JBossAS-5.1.0.GA
Reporter: Andriy Hnativ
Attachments: 2.patch
Original Estimate: 2 hours
Remaining Estimate: 2 hours
With the current JBoss 5.1.0 GA distribution it seems impossible to redirect to the port
that an external web server (like IIS) listens on (for example, to make AJP connector
redirect to the port 443 if the SSL port of the IIS configured to listen on 443), as the
xslt part in the JBoss>\server\<server>\conf\bindingservice.beans\META-INF\
bindings-jboss-beans.xml will change the "redirectPort" values defined in the
<JBoss>\server\<server>\jbossweb.sar\server.xml to the one defined in the
variable 'portHttps'. Changing the value of that variable will not work, as in
that case the xslt will change the "port" value of the SSL/TLS connector defined
in the server.xml, and it will try to connect to the same port as the one the external web
server already listens on.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira