[
https://issues.apache.org/jira/browse/NIFI-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Grey updated NIFI-10365:
-----------------------------
Description:
The current implementation of processor `InvokeHTTP` supports specification of
flowfile attributes to send as HTTP headers via processor property `Request
Header Attributes Pattern`. This property is a regex, and is immutable while
the processor is running.
In some situations, it would be helpful to dynamically specify attributes to
send as HTTP headers. So some InvokeHTTP invocations would send HTTP headers A
and B, while others would send headers B and C.
One possible implementation would involve the interpretation of an incoming
flowfile attribute value to serve the role currently filled by `Request Header
Attributes Pattern`.
was:
The current implementation of processor `InvokeHTTP` supports specification of
flowfile attributes to send as HTTP headers via processor property `Request
Header Attributes Pattern`. This property is a regex, and is immutable while
the processor is running.
In some situations, it would be helpful to dynamically specify attributes to
send as HTTP headers. So some InvokeHTTP invocations would send HTTP headers A
and B, while others would send headers B and C.
One possible implementation would involve the interpretation of an incoming
flowfile attribute value to serve the role currently filled by `Request Header
Attributes Pattern`.
> InvokeHTTP: support dynamic specification of "Request Header Attributes
> Pattern"
> --------------------------------------------------------------------------------
>
> Key: NIFI-10365
> URL: https://issues.apache.org/jira/browse/NIFI-10365
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Paul Grey
> Priority: Minor
>
> The current implementation of processor `InvokeHTTP` supports specification
> of
> flowfile attributes to send as HTTP headers via processor property `Request
> Header Attributes Pattern`. This property is a regex, and is immutable while
> the processor is running.
> In some situations, it would be helpful to dynamically specify attributes to
> send as HTTP headers. So some InvokeHTTP invocations would send HTTP headers
> A and B, while others would send headers B and C.
> One possible implementation would involve the interpretation of an incoming
> flowfile attribute value to serve the role currently filled by `Request
> Header Attributes Pattern`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
