Weird... So we do not have telnet, but I tried again and it worked
successfully, but only within the same cluster (VMs that the worker nodes
are running on). Performing a curl from the VM that contains the ncm yields
a "curl: (7) couldn't connect to host". Likewise for performing a curl from
other VMs even if we are on the same subnet.
I would like to be able to use a non-NiFi server, like NodeJS, to send an
HTTP request to NiFi. Is there a way I can do that?
Mark Payne wrote
> Dale,
>
> That should work. I tried exactly that and go the result below.
>
> Can you verify that your ListenHTTP processor is running and that it
> doesn't show any bulletins?
> Have tried to telnet in? I.e., "telnet
> <hostname>
> 8011" to see if you can connect that way?
>
> $ curl -i -X POST -H 'Content-Type: application/json' -d '{"test": "Hello,
> NiFi"}' http://localhost:8011/contentListener
> HTTP/1.1 200 OK
> Date: Tue, 14 Jun 2016 22:00:53 GMT
> Content-Type: text/plain
> Content-Length: 0
> Server: Jetty(9.2.11.v20150529)
>
> Thanks
> -Mark
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/ListenHTTP-Questions-tp11441p11462.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
