[jboss-jira] [JBoss JIRA] (WFLY-7031) Redirect Port Fails to Redirect to 3rd Party HTTP Port

[Daniele Pirola (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-7031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13358095#comment-13358095 ] 

Daniele Pirola commented on WFLY-7031:
--------------------------------------

Hi Bhaskara,
I have the same problem with wildfly 10.1.0.Final behind squid and apache httpd.
Finally I modify the {{ajp-listener}} specifying the attribute {{scheme}} like this:

{{ <ajp-listener name="ajp" socket-binding="ajp" *scheme="https"*/>}}

Now https call works fine and also redirect from http to https.
Probably this configuration could be more publicized inside wildfly documentation

> 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
(v7.2.3#72005)