[
https://issues.apache.org/jira/browse/NIFI-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089483#comment-15089483
]
Aldrin Piri commented on NIFI-1362:
-----------------------------------
[~jeremy.dyer], sorry for a bit of a delay, was trying to wrap up a few other
issues/patches yesterday.
I think we've run into some interesting scenarios and may need to adjust some
of the logic. The use case you show in your patch is good, but then it uses
the response content type to set the mime.type of the request FlowFIle. I feel
like the intent here is to provide a response.mime.type property or similar,
because otherwise, we are asserting that the request flowfile's content type is
that of the response which works for the test case because they are the same,
but potentially puts us down the wrong course. Consider the slightly contrived
scenario where I am perhaps POSTing an image/jpg picture to a site and
receiving text/plain in my response with some metadata about it.
Thoughts?
> Set mime.type attribute based on InvokeHTTP response Content-Type
> -----------------------------------------------------------------
>
> Key: NIFI-1362
> URL: https://issues.apache.org/jira/browse/NIFI-1362
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 0.4.1
> Reporter: Jeremy Dyer
> Assignee: Jeremy Dyer
> Priority: Minor
> Attachments: NIFI-1362.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Upon receiving a response from InvokeHTTP the mime.type attribute should be
> set to better help end users determine what kind of content was returned in
> the response
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
