[
https://issues.apache.org/jira/browse/NIFI-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18011188#comment-18011188
]
David Handermann commented on NIFI-14805:
-----------------------------------------
No problem, thanks for highlighting the lack of clarity! I changed this to an
improvement and submitted a pull request to update the description of the
Response relationship.
> 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: Improvement
> Components: Extensions
> Affects Versions: 2.2.0, 2.4.0
> Reporter: Marlies Hinterleitner
> Assignee: David Handermann
> Priority: Minor
> Attachments: Problem_with_InvokeHTTP.json
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> **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)
