[jboss-jira] [JBoss JIRA] (WFLY-3368) Reverse proxy configuration should use outbound-socket-binding

[Matt Wringe (JIRA)]

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

Matt Wringe commented on WFLY-3368:
-----------------------------------

Most of the other configuration options do accept variables, so this should also be able to do so.

Its also needed if you are running on something like openshift, where you want to use the reverse proxy on an internal IP address but on a port which is not exposed in openshift. So in this case, my host would be something like http://${env.OPENSHIFT_IP}:${env.SOMEPORT}. In this case, I don't know the IP address of the host before hand and need to use a variable.

> Reverse proxy configuration should use outbound-socket-binding
> --------------------------------------------------------------
>
>                 Key: WFLY-3368
>                 URL: https://issues.jboss.org/browse/WFLY-3368
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Undertow)
>    Affects Versions: 8.0.0.Final
>            Reporter: Matt Wringe
>            Assignee: Tomaz Cerar
>             Fix For: 9.0.0.Alpha1
>
>
> The reverse proxy configuration in standalone.xml requires a string value and will not accept variables like most of the other options.
> for example, something like this should be valid, but its currently not:
> {code:xml}
> <handlers>
>   <reverse-proxy name="reverse-proxy" connections-per-thread="30">
>     <host name="${myURL}" instance-id="myRoute"/>
>   </reverse-proxy>
> <handlers>
> {code}
> Here you need to specify the name as something like "http://127.5.183.1:8080"



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)