Aldrin, Bryan I think the point is to route the orig flowfile based on analyzing the content of the web response. The setup would be more involved On Aug 4, 2015 8:52 AM, "Aldrin Piri" <aldrinp...@gmail.com> wrote:
> Steve, > > 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 <stephen.c.metc...@lmco.com> 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: > > > http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/Route-Original-Flow-File-Base-on-InvokeHTTP-Response-tp2317p2324.html > > Sent from the Apache NiFi (incubating) Developer List mailing list > archive > > at Nabble.com. > > >
