[ 
https://issues.apache.org/jira/browse/NIFI-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049615#comment-16049615
 ] 

ASF GitHub Bot commented on NIFI-4019:
--------------------------------------

Github user jtstorck commented on the issue:

    https://github.com/apache/nifi/pull/1900
  
    @mcgilman There are a couple issues with the proxying support:
    * When the proxy that sets the X-Forwarded-* headers is running on a 
non-standard port for HTTP or HTTPS, the "X-Forwarded-Host" header value can 
contain the host and the port, such as localhost:8008 or localhost:8443.
    * There are some resources that are at absolute paths, like in nifi-docs.  
The documentation is showing up, but the css isn't loading.
    * If the NiFi service is terminated, and the NiFi client UI shows its 
general error page, the "home" link  does not point the browser back at the 
proxy's URL for NiFi.


> Add support for X-Forward-* headers
> -----------------------------------
>
>                 Key: NIFI-4019
>                 URL: https://issues.apache.org/jira/browse/NIFI-4019
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.2.0
>            Reporter: Jeff Storck
>            Assignee: Matt Gilman
>
> Extend NiFi proxy support by allowing the usage of the following headers:
> || Header || Purpose ||
> | X-Forwarded-Proto | the scheme used to connect to the proxy
> | X-Forwarded-Host | the host of the proxy
> | X-Forwarded-Port | the port on which the proxy is listening
> | X-Forwarded-Context | the the context path of the request to the proxy
> A mapping exists for the X-Forwarded-* headers to the currently supported 
> X-Proxy* headers:
> || X-Forwarded Header || X-Proxy Header ||
> | X-Forwarded-Proto | X-ProxyScheme
> | X-Forwarded-Host | X-ProxyHost
> | X-Forwarded-Port | X-ProxyPort
> | X-Forwarded-Context | X-ProxyContextPath



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to