You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/02/26 10:14:18 UTC

[jira] [Created] (QPID-7107) Http Management should be deployable behind a forwarder such as Apache HTTPD

Keith Wall created QPID-7107:
--------------------------------

             Summary: 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org