nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aldrin Piri <>
Subject Re: Route Original Flow File Base on InvokeHTTP Response
Date Tue, 04 Aug 2015 12:51:23 GMT

Building on the template Bryan provided you can route a successful response
to perform further inspection. Depending on content any of RouteOnContent
or EvaluateJsonPath/EvaluateXPath in conjunction with RouteOnAtrribute
could be viable options.

Let us know if this helps with the use case you are tackling or if there
are any other questions.

Sent from my mobile device.
On Tue, Aug 4, 2015 at 07:32 steveM <> wrote:

> Thanks for the quick response. However, my use case requires that I parse
> the
> actual response (not just make sure the response code is 200) to make a
> decision on routing.
> --
> View this message in context:
> Sent from the Apache NiFi (incubating) Developer List mailing list archive
> at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message