[
https://issues.apache.org/jira/browse/NIFI-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089367#comment-15089367
]
ASF subversion and git services commented on NIFI-1361:
-------------------------------------------------------
Commit 317b2f4a4aae43a3312b704eebe78ece0bf448a5 in nifi's branch
refs/heads/master from [~aldrin]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=317b2f4 ]
NIFI-1361 Exposing Content-Type as a processor property for both InvokeHTTP and
PostHTTP. This makes use of the mime.type attribute via the EL expression
${mime.type}, making more apparent to the user how this header is derived and
allowing the explicit setting of a value.
> Expose the Content-Type used for Invoke/PostHTTP
> ------------------------------------------------
>
> Key: NIFI-1361
> URL: https://issues.apache.org/jira/browse/NIFI-1361
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 0.4.1
> Reporter: Aldrin Piri
> Assignee: Aldrin Piri
> Priority: Minor
> Fix For: 0.5.0
>
> Attachments: NIFI-1361.0001.patch
>
>
> InvokeHTTP and PostHTTP make use of the mime.type attribute. While this is
> in documentation, it is not as apparent to the user and kind of applied
> behind the scenes. What would be nice is to have a property that brings this
> to the forefront in the processor configuration and shows that this is mapped
> to the EL ${mime.type}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
