That's an interesting service, must expect smallish files :) You can
get the entire content into an attribute using ExtractText, match the
whole thing and put it in an attribute called "file", then set the
Attributes To Send property in InvokeHttp to include "file" and
anything else (except Content
The service I am calling expects the content to be in an http post
attribute called "file". Using the guidance from you above Matt (thanks
very much for that), I have been able to post in attribute "file" some
random text, "@/home/nifi/test/dummyfilename.txt". I see that as output
from a ListenTTP
Jim,
The content of the flow file is the body of the outgoing POST, so you
could query provenance for the PostHttp processor, find the associated
flow file(s), and (if the content is still available in the content
repository) retrieve the content. Also the resolved URL for the POST
(after evaluati
But isn't the Http *response *what comes back to us? I like your thinking,
but it is the outgoing post i need to review. The response won't help me
with that. Am I missing the point?
On Wed, Nov 8, 2017 at 8:52 AM, Mike Thomsen wrote:
> Don't know, but you might want to try out InvokeHttp. I kno
Don't know, but you might want to try out InvokeHttp. I know it lets you
tap into the output if you tell it to always output the HTTP response.
On Wed, Nov 8, 2017 at 8:28 AM, James McMahon wrote:
> How can we tap into the workflow to see the output of the PostHTTP
> processor? What are options
How can we tap into the workflow to see the output of the PostHTTP
processor? What are options folks have used to do that?
Thanks in advance. -Jim
