[
https://issues.apache.org/jira/browse/NIFI-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193166#comment-15193166
]
ASF GitHub Bot commented on NIFI-1620:
--------------------------------------
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/272#issuecomment-196284703
Thank you @pvillard31 . That does make sense and in the case that there is
no request body being sent over I am supportive of the notion of not sending
the content type header. This also seems in line with Adam's rfc reference.
You want to tweak this PR then to retain existing content header logic but
rather have a 'send body' property or something which when false will not send
the body and will not set that header?
> 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: 0.6.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)
