[
https://issues.apache.org/jira/browse/NIFI-12875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17833805#comment-17833805
]
ASF subversion and git services commented on NIFI-12875:
--------------------------------------------------------
Commit 84df025ccfe68bf9eefc0a43ad14fdc727e3723d in nifi's branch
refs/heads/main from Gregory M. Foreman
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=84df025ccf ]
NIFI-12875 Added Response Handling Strategy to RestLookupService
This closes #8484
Signed-off-by: David Handermann <[email protected]>
> RestLookupService not handling HTTP 4xx/5xx error codes
> -------------------------------------------------------
>
> Key: NIFI-12875
> URL: https://issues.apache.org/jira/browse/NIFI-12875
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.0.0-M2
> Reporter: Gregory M. Foreman
> Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The RestLookupService service does not handle HTTP error codes correctly. If
> the web service being consumed returns a 4xx or 5xx error code, the
> RestLookupService service ignores the error and passes the response content
> to the record reader, causing unexpected exception reporting.
> Example: a web service that communicates with clients via JSON is behind a
> proxy. The proxy returns a 502 error and responds with HTML content
> describing the error. The RestLookupService uses a JsonTreeReader reader and
> attempts to parse the HTML characters. This leads to it throwing an
> exception that it was unable to parse the '<' character. The real reason is
> the proxy is sending back a 502 error, but this detail is hidden.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
