[
https://issues.apache.org/jira/browse/NIFI-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203636#comment-15203636
]
ASF GitHub Bot commented on NIFI-1620:
--------------------------------------
Github user taftster commented on the pull request:
https://github.com/apache/nifi/pull/272#issuecomment-199086081
This pull request is not strictly dealing with NIFI-1620. The edge case of
suppressing the Content-Type header for an empty message-body makes sense to
fix and address. NIFI-1620 is dealing with this edge case.
However, this PR is adding the ability to specify an HTTP request
message-body directly as a property of InvokeHTTP. In my opinion, this is not
a desired feature, and I am -1 on this. A static message-body can always be
provided in a dataflow using a tool like ReplaceText; keeping the semantics
that InvokeHTTP always reads from flowfile payloads has a good consistency.
Recommend that this PR focus solely on the problem dealing with
Content-Type of an empty payload for a POST/PUT operation. Another JIRA can be
opened to discuss the merits of how to provide static content to an HTTP
transaction.
> 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)
