[
https://issues.apache.org/jira/browse/MINIFI-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949167#comment-15949167
]
Andrew Christianson commented on MINIFI-239:
--------------------------------------------
[~phrocker] Right. It's all about this processor property, and how we map its
value to cURL:
```c++
core::Property InvokeHTTP::SSLContext(
"SSL Context Service",
"The SSL Context Service used to provide client certificate information for
TLS/SSL (https) connections.",
"");
```
AFAIK, there was not yet a concept of a SSLContext in MiNiFi, and maybe there
shouldn't be given that we want to stay lightweight. What you're saying
regarding the internal connections/implementation makes sense.
We'll think about possible designs/plans since it appears to be an open
question in MiNiFi at this point.
> Create a C++ HTTP client processor to match the InvokeHTTP processor
> --------------------------------------------------------------------
>
> Key: MINIFI-239
> URL: https://issues.apache.org/jira/browse/MINIFI-239
> Project: Apache NiFi MiNiFi
> Issue Type: Task
> Components: C++, Extensions
> Reporter: Andrew Grande
> Assignee: marco polo
>
> There is a ListenHTTP processor, but nothing for the client side (e.g. to
> invoke REST APIs). The civetweb library is already being used, can be
> leveraged to implement the InvokeHTTP parity.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
