[
https://issues.apache.org/jira/browse/MRESOLVER-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-629:
--------------------------------------
Description:
As JDK have no means to handle GOAWAYs we get more and more often. This is the
default setting that is being changed.
Users can still choose HTTP/2 by using
{{-Daether.transport.jdk.httpVersion=HTTP_2}} on CLI or in
{{.mvn/maven.config}} or user-wide in settings.xml.
Seems related issue fixed in Java 24?
https://bugs.openjdk.org/browse/JDK-8335181
was:
As JDK have no means to handle GOAWAYs we get more and more often. This is the
default setting that is being changed.
Users can still choose HTTP/2 by using
{{-Daether.transport.jdk.httpVersion=HTTP_2}} on CLI or in
{{.mvn/maven.config}} or user-wide in settings.xml.
> Make JDK transport default protocol HTTP/1.1
> --------------------------------------------
>
> Key: MRESOLVER-629
> URL: https://issues.apache.org/jira/browse/MRESOLVER-629
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.4
>
>
> As JDK have no means to handle GOAWAYs we get more and more often. This is
> the default setting that is being changed.
> Users can still choose HTTP/2 by using
> {{-Daether.transport.jdk.httpVersion=HTTP_2}} on CLI or in
> {{.mvn/maven.config}} or user-wide in settings.xml.
> Seems related issue fixed in Java 24?
> https://bugs.openjdk.org/browse/JDK-8335181
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
