[
https://issues.apache.org/jira/browse/NIFI-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013001#comment-15013001
]
ASF subversion and git services commented on NIFI-1009:
-------------------------------------------------------
Commit 8c2323dc8d0e107f1a99898370c7515fa9603122 in nifi's branch
refs/heads/master from [~JPercivall]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8c2323d ]
NIFI-1086 Provide refactoring of InvokeHTTP
NIFI-980 Add support for HTTP Digest authentication to InvokeHttp
NIFI-1080 Provide additional InvokeHttp unit tests
NIFI-1133 InvokeHTTP Processor does not save Location header for 3xx responses
NIFI-1009 InvokeHTTP should be able to be scheduled without any incoming
connection for GET operations
NIFI-61 Multiple improvements for InvokeHTTP inclusive of providing unique
tx.id across clusters, dynamic HTTP header properties
Signed-off-by: Aldrin Piri <[email protected]>
> InvokeHTTP should be able to be scheduled without any incoming connection for
> GET operations
> --------------------------------------------------------------------------------------------
>
> Key: NIFI-1009
> URL: https://issues.apache.org/jira/browse/NIFI-1009
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Joseph Percivall
> Fix For: 0.4.0
>
>
> Many users have been confused by InvokeHTTP not running when it is a "Source"
> processor. It probably doesn't make sense to do a POST or a PUT operation
> without an incoming FlowFile. However, if the Processor is configured to do a
> GET or DELETE, it should be able to run as a Source processor.
> Validation logic should indicate that the processor is not valid if it has no
> incoming connection and is configured to perform a POST or a PUT.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
