[NIFI-8454] InvokeHTTP does not report final URL after following redirects

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.13.2
• Fix Version/s: 1.14.0
• Labels: InvokeHTTP
• Assignee: Paul Kelly
• Reporter: Paul Kelly
• Created: 21/Apr/21 14:12
• Updated: 21/Apr/21 23:19
• Resolved: 21/Apr/21 23:19

Description

If InvokeHTTP is set to follow redirects, there currently is no way to retrieve the final URL which was the ultimate target of any redirects that were followed.

I propose adding a new attribute "invokehttp.response.url" to include the final URL when InvokeHTTP is set to follow redirects.  The current attribute "invokehttp.request.url" contains the URL which was originally requested, and this new attribute will contain the URL that was ultimately retrieved.

For example, if the URL "http://bitly.com/1sNZMwL" is retrieved, invokehttp.request.url will continue to contain "http://bitly.com/1sNZMwL" and invokehttp.response.url will contain "https://en.wikipedia.org/wiki/Bitly".

Issue Links

• links to: GitHub Pull Request #5016