[NIFI-4413] Content Viewer not working when cluster is behind reverse proxy - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Critical
Resolution: Fixed
Affects Version/s: 1.3.0
Fix Version/s: 1.4.0
Component/s: Core UI
Labels:
None
Environment:
Amazon Linux, CentOS 6 & 7

Description

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

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

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.