[
https://issues.jboss.org/browse/WFLY-7031?page=com.atlassian.jira.plugin....
]
Tomaz Cerar closed WFLY-7031.
-----------------------------
Assignee: Tomaz Cerar (was: Stuart Douglas)
Resolution: Rejected
This is not an issue at all.
It is just misconfiguration and nothing else.
You need to configure secure port binding for http-listener so server knows to what https
port to redirect if needed to. See "redirect-socket" config on http-listener
I think easiest for you would be to just upgrade to WildFly 10.1.0.Final which by default
comes with https-listener configured and also redirect ports.
Redirect Port Fails to Redirect to 3rd Party HTTP Port
------------------------------------------------------
Key: WFLY-7031
URL:
https://issues.jboss.org/browse/WFLY-7031
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 10.0.0.CR1
Reporter: Joe Carder
Assignee: Tomaz Cerar
Priority: Minor
When setting a redirect socket to port not opened by Wildfly (IE: a port opened by Apache
HTTPD or IIS), Wildfly throws the following exception:
ERROR [io.undertow.request] (default task-2) UT005001: An exception occurred processing
the request: java.lang.IllegalStateException: UT010053: No confidential port is available
to redirect the current request.
With the redirect socket to a port opened by JBoss, it works as expected. I'm not
100% sure this is a bug, or functional decision made for Wildfly 10 and is working as
expected. However, in Previous Widlfly version (Widlfly 8) it was possible to set the
redirect port to a third party service without out issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)