[
https://issues.apache.org/jira/browse/NIFI-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16182598#comment-16182598
]
ASF subversion and git services commented on NIFI-4413:
-------------------------------------------------------
Commit d47bbd12ce41d2bfebf255e303cbeb95362e7888 in nifi's branch
refs/heads/master from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=d47bbd1 ]
NIFI-4413: - Using the incoming request to determine the appropriate scheme for
the data reference URI. Necessary for cases where the NiFi instance is behind a
proxy running a different scheme.
This closes #2179.
Signed-off-by: Bryan Bende <[email protected]>
> Content Viewer not working when cluster is behind reverse proxy
> ---------------------------------------------------------------
>
> Key: NIFI-4413
> URL: https://issues.apache.org/jira/browse/NIFI-4413
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 1.3.0
> Environment: Amazon Linux, CentOS 6 & 7
> Reporter: Richard St. John
> Priority: Critical
> Attachments: Screen Shot 2017-09-24 at 1.03.23 PM.png, Screen Shot
> 2017-09-24 at 1.03.33 PM.png
>
>
> As a clustered NiFi user I need to be able to use the configurable NiFi
> content viewer to view flow file content. Currently, it works perfectly if
> the cluster is NOT behind a reverse proxy, like nginx, or AWS load balancer.
> It appears that the ref URL is not being properly formed or appropriate
> headers are not being sent with the view content request. Below is an
> example of the issue with another example where a modified URL does work.
> NOTE: URLs will not be reachable and are presented in this ticket for
> illustrative purposes, but the attached screenshots show the effect of the
> URLs
> DOES NOT WORK:
> https://nifi-gray.unrulyfire.com/nifi-content-viewer/?ref=https%3A%2F%2Fnifi-gray.unrulyfire.com%3A443%2Fnifi-api%2Fflowfile-queues%2Fb4aa9ade-015e-1000-ffff-ffff8856fa2d%2Fflowfiles%2Fb7c9b786-b85c-4feb-83a2-00bfcd0ffad5%2Fcontent%3FclusterNodeId%3D8b0cc92a-6266-4f3d-bcb0-95d994086c80
> !Screen Shot 2017-09-24 at 1.03.23 PM.png|thumbnail!
> DOES WORK :
> https://nifi-gray.unrulyfire.com/nifi-content-viewer/?ref=http%3A%2F%2F172.31.40.138%3A8080%2Fnifi-api%2Fflowfile-queues%2Fb4aa9ade-015e-1000-ffff-ffff8856fa2d%2Fflowfiles%2Fb7c9b786-b85c-4feb-83a2-00bfcd0ffad5%2Fcontent%3FclusterNodeId%3D8b0cc92a-6266-4f3d-bcb0-95d994086c80
> !Screen Shot 2017-09-24 at 1.03.33 PM.png|thumbnail!
> Note that the working example replaces the ref URL with an internal nifi node
> IP/URI
> I would be happy to work the issue, but I have been unable to figure out
> where these request parameters are collected.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
