[
https://issues.apache.org/jira/browse/NIFI-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899925#comment-17899925
]
ASF subversion and git services commented on NIFI-13491:
--------------------------------------------------------
Commit aa3a7c05adaaf0160b56516001cc8c2c3273b046 in nifi's branch
refs/heads/main from NissimShiman
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=aa3a7c05ad ]
NIFI-13491 Added Response Header Request Attributes Prefix to InvokeHTTP (#9507)
Signed-off-by: David Handermann <[email protected]>
> InvokeHTTP new property - Response Header Request Attributes Prefix
> -------------------------------------------------------------------
>
> Key: NIFI-13491
> URL: https://issues.apache.org/jira/browse/NIFI-13491
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Nissim Shiman
> Assignee: Nissim Shiman
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> InvokeHTTP has a property, _Response Header Request Attributes Enabled_ which
> is false by default.
> When it it set to true, the header request attributes are sent back and
> included as flowfile attributes on the _Original_ relationship, but there is
> nothing that indicates that the attributes refer to the response (as opposed
> to the flowfile contents that were sent).
> There will be new attributes of _Content-Type_ and _Content-Length_ with
> values that may be confusing to downstream users as they refer to the
> response, as opposed to the actual flowfile contents.
> This property will allow a prefix to be set, so that flow users will better
> understand that these refer to the http response.
> This option will only appear if _Response Header Request Attributes Enabled_
> is true.
> By default there will be no default value to allow backward compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
