You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2021/02/12 22:10:00 UTC
[jira] [Commented] (NIFI-5623) Update all usage of Okhttp to latest
library
[ https://issues.apache.org/jira/browse/NIFI-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284015#comment-17284015 ]
David Handermann commented on NIFI-5623:
----------------------------------------
NIFI-8181 incorporated an update from 3.8.1 to 4.9.0 in nifi-standard-bundle for InvokeHTTP. Other uses of OkHttp still need to be evaluated and updated.
> Update all usage of Okhttp to latest library
> --------------------------------------------
>
> Key: NIFI-5623
> URL: https://issues.apache.org/jira/browse/NIFI-5623
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Joe Witt
> Assignee: David Handermann
> Priority: Major
>
> In looking at existing dep usage and available versions we see
> [INFO] com.squareup.okhttp3:mockwebserver ................... 3.6.0 -> 3.11.0
> [INFO] com.squareup.okhttp3:okhttp ......................... 3.10.0 -> 3.11.0
> [INFO] com.squareup.okhttp3:okhttp .......................... 3.3.1 -> 3.11.0
> [INFO] com.squareup.okhttp3:okhttp .......................... 3.6.0 -> 3.11.0
> [INFO] com.squareup.okhttp3:okhttp .......................... 3.8.1 -> 3.11.0
> But in changing to 3.11.0 it became clear we have work to do so we can better leverage okhttp and its improving/tightening features around things like TLS setup/cert validation/hostname verification. Several tests started failing after the update. We need to use certs with updated SANs and we need to probably improve things as called out in https://issues.apache.org/jira/browse/NIFI-1478.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)