Thank you for your response Kevin & Jeff.
I could not figure out a way to get the original request that was sent by
Nginx to NiFi. So I'm going to try and provide you with other information
that might give you some insights into the headers that are being forwarded
to NiFi's embedded web server -
Swarup,
Agreed with Kevin, very nice write-up on the scenario!
Would you please provide the original request as sent by Nginx, along with
your configuration pertaining to NiFi in Nginx? We can set up some test
cases to reproduce what's happening and get a JIRA filed if there's an edge
case not
Swarup,
First, thanks for the great email. Nice job troubleshooting this and
sharing your findings with the community.
I'm more familiar with how these types of things get configured on
NiFi Registry than NiFi, so I'm not as much help as others. But I did
take a look and one thing I noticed was
Greetings,
I have deployed a single node unsecured NiFi cluster (I say cluster because
nifi.cluster.is.node is set to "true") as a stateful set on Kubernetes (AWS EKS
to be specific). The NiFi cluster sits behind an Nginx ingress. I have
configured the Nginx ingress to forward the appropriate
