The multipart/form-data body would have to be preemptively created and stored in your flowfile payload. InvokeHTTP could then be used to POST the message body to the remote server (after having set the appropriate content-type).
i.e. you have to manually construct the multipart form in the flowfile payload itself, the NIFI processors aren't going to do that for you like curl does. Does that make sense? On Mon, Jun 26, 2017 at 1:44 PM, icreatedanaccount < pierluc.boudr...@gmail.com> wrote: > I know they work great for sending parameters in the request headers, but > does the PostHTTP and InvokeHTTP processors support multipart/form-data as > a > content Content-Type ? > > Imagine something like this in CURL : > curl -v -X POST -F "file=@/19010230.bin" > > Best, > Luc > > > > -- > View this message in context: http://apache-nifi-developer- > list.39713.n7.nabble.com/Does-PostHTTP-support-Multipart- > form-data-tp16259.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >