[
https://issues.apache.org/jira/browse/NIFI-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203642#comment-15203642
]
ASF GitHub Bot commented on NIFI-1620:
--------------------------------------
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/272#issuecomment-199086549
@pvillard31 If you stay focused on the goal of NIFI-1620 here and avoid the
body manipulation this seems like a good step. Clearly you found a case worthy
of support (null body means unset or empty strong content type). But, i do
share Adam's view that it is best to avoid the content manipulation here. Do
you agree or do you feel like for the use case(s) you envisioned this would be
problematic?
Thanks
> 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
>
> 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)
