[
https://issues.jboss.org/browse/WFLY-3368?page=com.atlassian.jira.plugin....
]
Tomaz Cerar edited comment on WFLY-3368 at 7/28/14 5:06 PM:
------------------------------------------------------------
@matt Would something like this cover your scenarios:
{code:xml}
<reverse-proxy name="reverse-proxy"
connections-per-thread="30">
<host name="localhost" scheme="ajp"
path="/sub-resource"outbound-socket-binding-ref="ajp-remote"
instance-id="myRoute"/>
</reverse-proxy>
{code}
and later in config you have
{code:xml}
<outbound-socket-binding name="ajp-remote">
<remote-destination host="localhost" port="8009"/>
</outbound-socket-binding>
{code}
was (Author: ctomc):
@matt Would something like this cover your scenarios:
{code:xml}
<reverse-proxy name="reverse-proxy"
connections-per-thread="30">
<host name="localhost" scheme="ajp"
outbound-socket-binding-ref="ajp-remote" instance-id="myRoute"/>
</reverse-proxy>
{code}
and later in config you have
{code:xml}
<outbound-socket-binding name="ajp-remote">
<remote-destination host="localhost" port="8009"/>
</outbound-socket-binding>
{code}
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)