[
https://issues.apache.org/jira/browse/NIFI-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022280#comment-16022280
]
ASF GitHub Bot commented on NIFI-1490:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/1795
hello @pipern. Thanks for contributing. If i'm reading this right it
looks like what this will do is grab the first matching section of a multi-part
request. The current behavior before the patch would be to, i believe, grab
all of the request as the flow file content. Given that, it seems like rather
than altering this processor to grab just the first match we'd either want to
alter it to grab each section as new flow files OR perhaps better yet have a
different processor which understands how to extract out the specific parts
into individual flowfiles. ExtractMultiPartHttp for example could take as
input the entire request body in a flowfile that came from ListenHTTP and this
new processor could create child objects which are each of the parts.
What do you think about that?
> Add multipart request support to ListenHTTP Processor
> -----------------------------------------------------
>
> Key: NIFI-1490
> URL: https://issues.apache.org/jira/browse/NIFI-1490
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Andrew Serff
>
> The current ListenHTTP processor does not seem to support multipart requests
> that are encoded with multipart/form-data. When a multipart request is
> received, the ListenHTTPServlet just copies the Request InputStream to the
> FlowFiles content which leaves the form encoding wrapper in the content and
> in turn makes the file invalid.
> Specifically, we want to be able to support file uploads in a multipart
> request.
> See this thread in the mailing list for more info:
> http://mail-archives.apache.org/mod_mbox/nifi-users/201602.mbox/%3C6DE9CEEF-2A37-480F-8D3C-5028C590FD9E%40acesinc.net%3E
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
