[
https://issues.apache.org/jira/browse/NIFI-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188802#comment-17188802
]
Zack Atkinson commented on NIFI-7588:
-------------------------------------
We hit this in production. Initially we thought our source blocked our
ip-address because changing hosts fixed the problem. Turns out copying the NiFi
processor gets its working again. Attached is a image of the debug statements
turned on for InvokeHTTP.
The first two statements are on the original processor giving us bad responses
because the "authorization" is not being passed in as expected. The seconds two
statements show the copied InvokeHTTP processor working correctly passing the
authorization correctly to the processor.
> InvokeHTTP ignoring custom parameters when stop+finalize+start
> --------------------------------------------------------------
>
> Key: NIFI-7588
> URL: https://issues.apache.org/jira/browse/NIFI-7588
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.11.4
> Environment: Amazon Linux
> Reporter: Alejandro Fiel Martínez
> Priority: Major
> Attachments: invokeHTTP_NiFi_bug.png
>
>
> I have an InvokeHTTP processor, with 3 custom paramenters to be passed as
> headers, If I add an SSL Context Service and remove it, the processor stop
> using those 3 paramenters and I have to delete and recreate then, they are
> there, but I see in DEBUG that there are not used in the GET request.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
