You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Aptly named, the OkHttp3ClientHttpRequestFactory is based on OkHttp 3. Since the introduction of this type, OkHttp4 has been released, which is binary compatibly with 3, but it does require the Kotlin runtime. OkHttp 5 is currently in the works, and appears not backward compatible.
We should deprecate the OkHttp3ClientHttpRequestFactory, because it is unclear what kind of back porting policy has, and because keeping an outdated dependency introduces security risks. Furthermore, the current and future implementation of OkHttp requires Kotlin at runtime, which makes it less suitable for Java usage.
New request factories have been introduced in 6.1 (see #30564, #30478, #30835), offering a wide choice of alternatives for the OkHttp3ClientHttpRequestFactory.
The text was updated successfully, but these errors were encountered:
Aptly named, the
OkHttp3ClientHttpRequestFactory
is based on OkHttp 3. Since the introduction of this type, OkHttp4 has been released, which is binary compatibly with 3, but it does require the Kotlin runtime. OkHttp 5 is currently in the works, and appears not backward compatible.We should deprecate the
OkHttp3ClientHttpRequestFactory
, because it is unclear what kind of back porting policy has, and because keeping an outdated dependency introduces security risks. Furthermore, the current and future implementation of OkHttp requires Kotlin at runtime, which makes it less suitable for Java usage.New request factories have been introduced in 6.1 (see #30564, #30478, #30835), offering a wide choice of alternatives for the
OkHttp3ClientHttpRequestFactory
.The text was updated successfully, but these errors were encountered: