[
https://issues.apache.org/jira/browse/NIFI-13982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13982:
------------------------------------
Fix Version/s: 2.1.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Web client - body as string and get request URI for response entity
> -------------------------------------------------------------------
>
> Key: NIFI-13982
> URL: https://issues.apache.org/jira/browse/NIFI-13982
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Minor
> Fix For: 2.1.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> In the web client API, we currently have in HttpRequestBodySpec:
> {code:java}
> HttpRequestHeadersSpec body(InputStream inputStream, OptionalLong
> contentLength) {code}
> It would be convenient to also have:
> {code:java}
> HttpRequestHeadersSpec body(String body); {code}
> Especially when the payload is very small and easy to craft.
> In addition, in HttpResponseEntity, there is no way to know what endpoint has
> been accessed to generate that response. Having the possibility to retrieved
> the requested endpoint from the response entity might be useful when there is
> a separation between processors and controller services, in particular when
> generating the provenance events at processor level where adding the transit
> URI is useful for data lineage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
