Skip to content

Update to Apache HttpClient 5. #1205

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

Open
elharo opened this issue Dec 16, 2020 · 8 comments
Open

Update to Apache HttpClient 5. #1205

elharo opened this issue Dec 16, 2020 · 8 comments
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@elharo
Copy link
Contributor

elharo commented Dec 16, 2020

HttpClient 5.0
HttpCore 5.1

This will be required to support HTTP/2. This is a big one so needs to be investigated carefully.

@chingor13 chingor13 added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Dec 16, 2020
@chingor13
Copy link
Collaborator

We likely would want another separate artifact like google-http-client-apache5

@chingor13
Copy link
Collaborator

We also probably need to drop the original apache client (that doesn't really work) that is packaged in google-http-client.

@elharo elharo changed the title Update to Apache Update to Apache HttpClient 5. Dec 21, 2020
@elharo
Copy link
Contributor Author

elharo commented Dec 21, 2020

I don't think we need a new google-http-client-apache5 and we can simply drop the old one. That is, this is no longer used. The real update needs to happen in core.

@elharo
Copy link
Contributor Author

elharo commented Jan 6, 2021

On further investigation, we probably do need a new artifact for this because the existing API exposes org.apache.http.client types in its public API and those types have changed in HTTP client 5. We probably shouldn't have done that, but that ship sailed long ago.

This time around let's see if we can avoid exposing third party types on our API surface.

@chingor13
Copy link
Collaborator

For context, we accept a fully configured Apache HttpClient instance otherwise we would basically be reimplementing the entire surface of the HttpClient builder to provide users the ability to configure the underlying Apache transport.

@meor9zcu12
Copy link

HTTP/2 is very important in my case, is there any plan to upgrade to HttpClient 5?
Some libraries use google-http-java-client as dependency, and hence I can't easily customize and override the Apache HttpClient implementation in these libraries.

@bc-bartvb
Copy link

So, what is the status. if any? Any plans? Our migration to Apache HTTP 5.x is now stuck because of this. If there are no plans, we will move away from using this library. There are now dependencies that are EOL.

@mjschwaiger
Copy link

mjschwaiger commented Apr 8, 2025

Are there any updates on this topic?
Last release of httpclient (version 4) was in November 2022 - more than 2 years ago ...

Is this google-http-client-apache-v5 the component which should be used for this purpose?
See #1960.

Please keep us informed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

5 participants