[ https://issues.apache.org/jira/browse/NIFI-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17580804#comment-17580804 ]
David Handermann commented on NIFI-5232: ---------------------------------------- NIFI-10244 implemented something similar to the capabilities described in this issue in a {{WebClientServiceProvider}} Controller Service and {{WebClientService}} abstraction. [~mike.thomsen] Perhaps this issue could be closed in light of that implementation? > HttpConnectionService controller service > ---------------------------------------- > > Key: NIFI-5232 > URL: https://issues.apache.org/jira/browse/NIFI-5232 > Project: Apache NiFi > Issue Type: New Feature > Reporter: Mike Thomsen > Priority: Major > > The functionality of InvokeHttp and related processors should be copied over > to a controller service that can do much the same thing. This controller > service would be able to handle all of the common scenarios with HTTP > connections from processors going forward. -- This message was sent by Atlassian Jira (v8.20.10#820010)