[
https://issues.apache.org/jira/browse/NIFI-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296612#comment-16296612
]
ASF GitHub Bot commented on NIFI-1490:
--------------------------------------
Github user pipern commented on the issue:
https://github.com/apache/nifi/pull/1795
Do you think it's worth it @joewitt , since maybe this PR should be
rejected and someone works on ExtractMultiPartHttp instead? (I'd like to, but
can't commit to it. Maybe over Christmas...)
The decision of ExtractMultiPartHttp vs. an extracting-ListenHTTP maybe
comes down to how we want errors send back to the client. If we want to be able
to tell the HTTP client that their MultiPart was not well-formed, we'd have to
do it in ListenHTTP, right? (Which potentially invalidates my first paragraph.)
> 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.4.14#64029)
