[
https://issues.apache.org/jira/browse/NIFI-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15333304#comment-15333304
]
Pierre Villard commented on NIFI-1620:
--------------------------------------
Thanks for the review [~adamtaft]! I'll update the PR to take into account your
comments.
Regarding the proposition to not transmit Content-Type when there is no
content, I think this could possibly break backward compatibility in case some
applications are expecting content type in any case (even with an empty
content), no?
I don't care if this is postponed, there is no blocking issue on my side but,
just as a remark, some flows I have worked on seem to be impossible without
this change (the main one is probably the one dealing with the Dropbox API).
> Allow empty Content-Type in InvokeHTTP processor
> ------------------------------------------------
>
> Key: NIFI-1620
> URL: https://issues.apache.org/jira/browse/NIFI-1620
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.5.1
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Fix For: 1.0.0, 0.7.0
>
>
> External API could expect a POST request without a Content-Type property or
> at least with this property empty:
> *Error example:*
> {quote}
> You provided a non-empty HTTP "Content-Type" header ("application/json").
> This API function requires that the header be missing or empty.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
