[
https://issues.apache.org/jira/browse/NIFI-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15779743#comment-15779743
]
ASF GitHub Bot commented on NIFI-3207:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/1334
Reviewed the change, all looks good!
I was able to reproduce the issue on a docker environment with an un-secure
NiFi cluster running behind a nginx which terminates SSL. Docker-compose file
is available
[here](https://github.com/ijokarumawak/nifi-integration-tests/blob/master/docker-compose-nginx-ssl-terminate-nifi-cluster.yml).
Then, confirmed that a template file can be uploaded after applying this PR.
Also, I double checked the usage of `isReplicateRequest()` and
`getRequestReplicator()` methods. Confirmed that
`ProcessGroupResource.uploadTemplate()` is the only one that construct URI
without using uriInfo.
Thanks for reporting this issue, @rstjohn , and the fix, @mcgilman !
I'm merging this into master.
> Incorrect URI generated when replicating Template upload request
> ----------------------------------------------------------------
>
> Key: NIFI-3207
> URL: https://issues.apache.org/jira/browse/NIFI-3207
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Priority: Minor
> Fix For: 1.2.0
>
>
> When replicating a request to upload a Template, the URI was being generated
> with consideration for the proxy headers. However, these values are only
> meant to be used in responses to clients, not during requests being
> replicated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
