[
https://issues.apache.org/jira/browse/NIFI-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-1341.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.5.0
> Enhance documentation surrounding the use of mime.type for POST/InvokeHTTP
> --------------------------------------------------------------------------
>
> Key: NIFI-1341
> URL: https://issues.apache.org/jira/browse/NIFI-1341
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website, Extensions
> Affects Versions: 0.4.1
> Reporter: Aldrin Piri
> Priority: Minor
> Fix For: 0.5.0
>
>
> It is a common case where a user would like to send data to a given endpoint
> that may have been created outside of NiFi and, accordingly, has some known
> format or type associated with it that the operator knows given its sourcing.
> In these cases, NiFi may not know that a file may be something like XML or
> JSON and defaults to more generic types like plain text or octet-stream.
> Both InvokeHTTP and PostHTTP make use of the CoreAttribute mime.type for
> establishing Content-Type on requests where a body is posted to a specified
> endpoint. We should make this process more clear from the documentation and
> consider ways to make this more intuitive for users to accomplish.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
