You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Mike Thomsen (Jira)" <ji...@apache.org> on 2022/08/23 16:44:00 UTC

[jira] [Resolved] (NIFI-5232) HttpConnectionService controller service

     [ https://issues.apache.org/jira/browse/NIFI-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Thomsen resolved NIFI-5232.
--------------------------------
    Resolution: Duplicate

[~exceptionfactory] yeah, I agree that your ticket resolved this. Thanks for bringing that up. I think adding your component to the scripting package might be a good idea for 1.18 because I've seen a lot of cases on our team where it might be helpful to script out some HTTP calls and really go to town on the responses (government systems, nasty output a lot of the time).

> 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)