[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=12988469#comment-12988469 ] 

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

I havn't looked into this lately, but I think it looks about right :) If you can get me a patch to try out I might be able to do a quick check within the next week or so.

For my usecase, if I tried to specified one particular port than it didn't work due to multiple connections and the socket already being in use (if you don't specify a port than it grabs one from a pool each time). So hopefully the 'port' option there is optional.

> 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.Beta1
>
>
> 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.6#6264)