[
https://issues.apache.org/jira/browse/NIFI-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396721#comment-16396721
]
ASF subversion and git services commented on NIFI-3402:
-------------------------------------------------------
Commit 6471f66acd763794f42c1bf968c7e53f04058e76 in nifi's branch
refs/heads/master from m-hogue
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=6471f66 ]
NIFI-3402 - Added etag support to InvokeHTTP
Signed-off-by: Pierre Villard <pierre.villard...@gmail.com>
This closes #2150.
> Add ETag Support to InvokeHTTP
> ------------------------------
>
> Key: NIFI-3402
> URL: https://issues.apache.org/jira/browse/NIFI-3402
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Brandon DeVries
> Assignee: Michael Hogue
> Priority: Trivial
> Fix For: 1.6.0
>
>
> Unlike GetHTTP, when running in "source" mode InvokeHTTP doesn't support
> ETags. It will pull from a URL as often as it is scheduled to run. When
> running with an input relationship, it would potentially make sense to not
> use the ETag. But at least in "source" mode, it seems like it should at
> least be an option.
> To maintain backwards compatibility and support the non-"source" usage, I'd
> suggest creating a new "Use ETag" property that defaults to false...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
