[NIFI-12875] Add Response Handling Strategy to RestLookupService

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-M2
• Fix Version/s: 2.0.0-M3
• Assignee: Gregory M. Foreman
• Reporter: Gregory M. Foreman
• Created: 07/Mar/24 17:48
• Updated: 04/Apr/24 03:16
• Resolved: 04/Apr/24 03:16

Description

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.

Issue Links

• duplicates: NIFI-7851 RestLookupService does not throw a LookupFailureException when the rest endpoint response-code is not successful.
• links to: GitHub Pull Request #8484
• links to: Mailing List Post