Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate OkHttp3ClientHttpRequestFactory #30919

Closed
poutsma opened this issue Jul 20, 2023 · 2 comments
Closed

Deprecate OkHttp3ClientHttpRequestFactory #30919

poutsma opened this issue Jul 20, 2023 · 2 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: task A general task
Milestone

Comments

@poutsma
Copy link
Contributor

poutsma commented Jul 20, 2023

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.

@swankjesse
Copy link

FYI, OkHttp 5 is strongly backwards-compatible.

@mpellicer
Copy link

Sorry for asking, what would be a good alternative in the next releases for this Factory and the 4.x series of the OkHttp client?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: task A general task
Projects
None yet
Development

No branches or pull requests

3 participants