[
https://issues.apache.org/jira/browse/QPID-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173828#comment-15173828
]
Keith Wall edited comment on QPID-7107 at 3/1/16 2:35 PM:
----------------------------------------------------------
When deploying WMC behind a Apache Httpd, I may want to re-home the
application, that is make it appear served from a different root. This allows
many applications to share the same forwarder, or even many web management
consoles.
{noformat}
ProxyPass "/myqpid" "http://localhost:8080/";
{noformat}
If I try the above configuration, the WMC mostly works, but the structure
servlet fails to load properly. It seems that the javascript assumes that the
structure servlet (service/structure) is served from the root. It should not
make this assumption. It should form its url relative to index.html.
{noformat}
fe80::e4d:e9ff:fea5:c7e1 - - [27/Feb/2016:20:39:28 +0000] "GET
/myqpidservice/structure HTTP/1.1" 404 221
{noformat}
was (Author: k-wall):
When deploying WMC behind a Apache Httpd, I may want to re-home the
application, that is make it appear served from a different root. This allows
may applications to share the same forwarder, or even many web management
consoles.
{noformat}
ProxyPass "/myqpid" "http://localhost:8080/";
{noformat}
If I try the above configuration, the WMC mostly works, but the structure
servlet fails to load properly. It seems that the javascript assumes that the
structure servlet (service/structure) is served from the root. It should not
make this assumption. It should form its url relative to index.html.
{noformat}
fe80::e4d:e9ff:fea5:c7e1 - - [27/Feb/2016:20:39:28 +0000] "GET
/myqpidservice/structure HTTP/1.1" 404 221
{noformat}
> Http Management should be deployable behind a forwarder such as Apache HTTPD
> ----------------------------------------------------------------------------
>
> Key: QPID-7107
> URL: https://issues.apache.org/jira/browse/QPID-7107
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
>
> For (HTTP) management purposes, the Broker may be deployed behind a forwarder
> such as Apache HTTP. Users would connect to Apache HTTP and their requests
> would be forwarded to the Broker.
> {{HttpRequestInteractiveAuthenticator}} implementations need to be able to
> generate HTTP redirects. These currently won't work when a forwarder is in
> use. HTTP Management plugin servlet's will see the hostname and port of the
> forwarder rather than the host and port to which the user connected.
> We need to allow Jetty's {{ForwardedRequestCustomizer}} to be enabled. This
> causes Jetty to rewrite the request headers of forwarded requests using
> information provided by the forwarder (Apache HTTP) in the X-Forwarded
> headers.
> http://download.eclipse.org/jetty/9.3.7.v20160115/apidocs/org/eclipse/jetty/server/ForwardedRequestCustomizer.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
