[
https://issues.apache.org/jira/browse/NIFI-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18011182#comment-18011182
]
David Handermann commented on NIFI-14805:
-----------------------------------------
Thanks for the describing the scenario and providing the flow definition
[~marlies].
The current behavior of the InvokeHTTP Processor is expected, based on the
description. However, it looks like it is worth adding a bit more to the
property description, indicating that it is regardless of the response "status
code" received.
> InvokeHTTP routes all responses to 'response' relationship regardless of HTTP
> status code
> -----------------------------------------------------------------------------------------
>
> Key: NIFI-14805
> URL: https://issues.apache.org/jira/browse/NIFI-14805
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 2.2.0, 2.4.0
> Reporter: Marlies Hinterleitner
> Priority: Minor
> Attachments: Problem_with_InvokeHTTP.json
>
>
> **Expected Behavior:**
> FlowFiles should be routed to `success`, `response`, or `failure` based on
> the HTTP status code and processor configuration.
> **Actual Behavior:**
> All FlowFiles are routed to `response`, regardless of the HTTP status code,
> when the property Response Generation Required is set to true. If this
> property is set to false, the failed responses are terminated correctly.
> **Steps to Reproduce:**
> 1. Create a flow with `InvokeHTTP` calling an API that returns 403.
> 2. Observe that the FlowFile is routed to `response` instead of `failure`.
> (See in Flow Definition below.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
