-
Notifications
You must be signed in to change notification settings - Fork 461
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
Comments
We likely would want another separate artifact like |
We also probably need to drop the original apache client (that doesn't really work) that is packaged in |
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. |
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. |
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. |
HTTP/2 is very important in my case, is there any plan to upgrade to HttpClient 5? |
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. |
Are there any updates on this topic? Is this google-http-client-apache-v5 the component which should be used for this purpose? Please keep us informed. |
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.
The text was updated successfully, but these errors were encountered: