[ 
https://issues.apache.org/jira/browse/NIFI-13619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bryan Bende updated NIFI-13619:
-------------------------------
    Fix Version/s: 2.0.0-M5
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

> Switch web-client Implementation from OkHttp to Java HttpClient
> ---------------------------------------------------------------
>
>                 Key: NIFI-13619
>                 URL: https://issues.apache.org/jira/browse/NIFI-13619
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>             Fix For: 2.0.0-M5
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> The nifi-web-client library currently implements the nifi-web-client-api 
> using the OkHttp library. The nifi-web-client library powers the 
> WebClientServiceProvider Controller Service, which several Processors use for 
> HTTP operations. OkHttp 4 is written in Kotlin and depends on several Kotlin 
> standard libraries. Although this approach provided broad compatibility in 
> initial versions supported Java 8, Java 9 and following have an HttpClient 
> class and supporting components. The Java HttpClient class supports all of 
> the standard operations required for the nifi-web-client library, including 
> support for HTTP/2 with TLS and proxy authentication. Switching the 
> nifi-web-client library away from OkHttp removes the several runtime 
> dependencies and provides general compatibility with current Java versions 
> for NiFi 2.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to