[ 
https://issues.apache.org/jira/browse/NIFI-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18011213#comment-18011213
 ] 

ASF subversion and git services commented on NIFI-14805:
--------------------------------------------------------

Commit d9b4984b1270f7659660e0ae58a52afe6a44f7e3 in nifi's branch 
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d9b4984b12 ]

NIFI-14805 Improved Response Relationship description for InvokeHTTP

- Indicated that enabling Response Generation Required changes routing behavior

Signed-off-by: Pierre Villard <[email protected]>

This closes #10151.


> 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: 1h 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)

Reply via email to