[jira] [Commented] (NIFI-14) Invoke HTTP Processor does not allow the sending certain NiFi paramaters as Http Headers

["Joseph Percivall (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081282#comment-15081282 ] 

Joseph Percivall commented on NIFI-14:
--------------------------------------

In the refactor of InvokeHttp, part of NiFi-61 [1] was to add the ability to "Support user dynamic http header properties."

The title of this ticket merely says that some attributes can't be sent because they're ignored (when the regex prop is being evaluated). That's obsolete because now we can create dynamic properties that are EL and evaluated against the FF. 

This ability to add dynamic properties that are evaluated as EL to send as Headers I think provides the greater configuration that is mentioned in the description. 

I'm marking as OBE.

[1] https://issues.apache.org/jira/browse/NIFI-61

> Invoke HTTP Processor does not allow the sending certain NiFi paramaters as Http Headers
> ----------------------------------------------------------------------------------------
>
>                 Key: NIFI-14
>                 URL: https://issues.apache.org/jira/browse/NIFI-14
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Joseph Witt
>            Priority: Minor
>
> Invoke HTTP should allow greater configuration options for controlling what does and does not get sent as HTTP Headers from flow file attributes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)