[
https://issues.apache.org/jira/browse/MINIFI-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949133#comment-15949133
]
marco polo commented on MINIFI-239:
-----------------------------------
[~achristianson], I'm uncertain what you mean by SSLContext. When I hear that
phrase I put my JAVA hat on and think of the java.net.ssl class. The closest
thing we have org::apache::nifi::minifi::io::StreamFactory, which will return a
unique_ptr of Socket. Socket will either be a raw BSD socket or a TLSSocket,
using OpenSSL. We also have TLSContext, which will return the SSL_CTX ptr for
OpenSSL.
TLSContext can be used within the following function:
https://curl.haxx.se/libcurl/c/CURLOPT_SSL_CTX_FUNCTION.html . This should give
us a relatively easy way to integrate into libCURL. The intent was that
TLSContext was abstracted behind the StreamFactory itself, but in the case like
this, since we're externalized, we may either need to make interfaces to more
seamlessly allow the integration or couple InvokeHTTP to TLSContext. In either
case, it's not quite as well integrated as SSLEngine is in JAVA. libCURL will
integrate with OpenSSL somewhat, though...
> 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)
