[ 
https://issues.apache.org/jira/browse/NIFI-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15087663#comment-15087663
 ] 

Aldrin Piri commented on NIFI-1361:
-----------------------------------

Updated to include the same set of tests for PUT and refactored the handlers to 
remove the duplicated code that was there.

Commit is available here: 
https://github.com/apiri/incubator-nifi/commit/ed0784288a89f9cdb8c5f5dd49a26d51dfd63031
 

With associated patch of:
https://github.com/apiri/incubator-nifi/commit/ed0784288a89f9cdb8c5f5dd49a26d51dfd63031.patch

> 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)

Reply via email to