[
https://issues.apache.org/jira/browse/MRESOLVER-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742025#comment-17742025
]
Konrad Windszus commented on MRESOLVER-384:
-------------------------------------------
At least connection pooling should work better, as there is a dedicated HTTP
message for ending a connection
(https://datatracker.ietf.org/doc/html/rfc9113#name-connection-error-handling)
so issues like MRESOLVER-383 should not happen with HTTP/2 (and yes, even with
HTTP/2 it is useful to use connection pooling)
> Support HTTP/2 in maven-resolver-transport-http
> -----------------------------------------------
>
> Key: MRESOLVER-384
> URL: https://issues.apache.org/jira/browse/MRESOLVER-384
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently transport-http relies on the outdated Apache HttpClient 4.5.x which
> does not support HTTP/2
> (https://hc.apache.org/httpcomponents-client-4.5.x/index.html).
> {quote}
> Standards based, pure Java, implementation of HTTP versions 1.0 and 1.1
> {quote}.
> The recommendation in https://hc.apache.org/status.html is
> {quote}
> Users of HttpClient 4.x are strongly encouraged to migrate to HttpClient 5.x
> {quote}
> In order to benefit from HTTP/2 connections to Maven Central we should
> upgrade to Apache HttpClient 5.x or some other library capable of HTTP/2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
