James,

I believe you need both.  StandardHttpContextMap caches request information
between a pair of HandleHttpRequest and HandleHttpResponse processors and
the StandardSSLContextService provides server side encryption of the HTTPS
connection.

I don't think you mentioned a HandleHttpResponse processor, do you have one
to provide the web service response?  If not, look at
"Hello_NiFi_Web_Service" template on the Example Dataflow Templates
<https://cwiki.apache.org/confluence/display/NIFI/Example+Dataflow+Templates>
page.

Regards,
Joe S

On Wed, Sep 7, 2016 at 3:07 PM, James McMahon <[email protected]> wrote:

> I tried to POST to HandleHTTPRequest from Python, but it is not working. I
> noticed that I've got StandardHttpContextMap configured in this processor.
> I am using a secure https NiFi instance; instead of StandardHttpContextMap,
> should I be configuring this processor with StandardSSLContextService?
> Thank you.
>
> On Sun, Sep 4, 2016 at 8:22 AM, Matt Burgess <[email protected]> wrote:
>
>> James,
>>
>> For simple calls that return immediately, ListenHttp probably works
>> fine. For more flexible and powerful processing of HTTP requests (and
>> responses), you might be better off with HandleHttpRequest and
>> HandleHttpResponse. There is an example of this under
>> Hello_NiFi_Web_Service [1].
>>
>> Regards,
>> Matt
>>
>> [1] https://cwiki.apache.org/confluence/display/NIFI/Example+
>> Dataflow+Templates
>>
>> On Sun, Sep 4, 2016 at 7:40 AM, James McMahon <[email protected]>
>> wrote:
>> > I have a series of applications, each of which I need to redesign so
>> that
>> > they post raw data to NiFi. Is there an example showing how to to
>> construct
>> > and execute RESTful calls that push data to NiFi? My assumption is that
>> I
>> > would establish a ListenHTTP processor in my workflow to receive the
>> > incoming content. Is that correct, or should this be handled
>> differently? My
>> > apps are in java and are simple, so I can readily port them to nodeJS,
>> > Python, Groovy, etc. Thanks in advance for your help.
>>
>
>

Reply via email to