Joe P, Do you have any other recommendations light of the work you're doing now to Invoke HTTP?
Thanks Joe On Sun, Nov 8, 2015 at 9:49 PM, M Singh <mans2si...@yahoo.com> wrote: > Thanks Joe. > > When I look at the provenance of the flow file, it shows the status as 301 > as shown below but no Location attribute. > > If I curl the url and check the headers it does show the Location attribute. > > invokehttp.status.code 301 > > > > > On Sunday, November 8, 2015 4:58 PM, Joe Witt <joe.w...@gmail.com> wrote: > > > Hello > > You can use provenance or a LogAttributes processor to see what the > headers are of the flow file after InvokeHTTP executes. You may find > the location header present as one of the attributes. If so then you > should be able to use that attribute to establish the URL it will hit > next time. Does that help? > > Thanks > Joe > > On Sun, Nov 8, 2015 at 7:51 PM, M Singh <mans2si...@yahoo.com> wrote: >> Hi: >> >> I am trying to use InvokeHTTP and have set the follow-retry to true, and >> have associated a self referencing relation for the InvokeHttp for >> no-retry >> (1xx, 2xx, and 3xx) and retry (5xx) relations. But it looks like it >> retires >> only status 500 codes requests and for 3xx does not pick up the Location >> header for retrying. >> >> However, since I am new to nifi - I might be missing something or using >> the >> wrong settings or wrong processor. >> >> If anyone has any suggestion, please let me know. >> >> Thanks >> > >
