[
https://issues.apache.org/jira/browse/NIFI-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192906#comment-15192906
]
ASF GitHub Bot commented on NIFI-1620:
--------------------------------------
Github user pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/272#issuecomment-196200486
Definitely agree with you that this API should not act this way.
Anyway, just to clarify, this is only in the case there is no body/content
sent with the request.
That's why, in a message on the mailing list, I suggested to add a "body"
property. If this property is set (possibly set to empty), the possible
(incoming relationship is not mandatory with this processor) incoming flow file
is ignored to set content and the request body is constructed with the
property. This way we can validate the empty content type if and only if body
is set to empty.
Let me know if that makes sense.
> 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)
