kwin opened a new issue, #1964: URL: https://github.com/apache/maven-resolver/issues/1964
### Affected version 2.0.20 ### Bug description Not consuming the response body can lead to stale http connections and in the end to deadlocks. The response body is not consumed in https://github.com/apache/maven-resolver/blob/79d102b66235f33ad1e6134e18451ac3ee91b44a/maven-resolver-transport-jetty/src/main/java/org/eclipse/aether/transport/jetty/JettyTransporter.java#L309 and not in https://github.com/apache/maven-resolver/blob/79d102b66235f33ad1e6134e18451ac3ee91b44a/maven-resolver-transport-jdk-parent/maven-resolver-transport-jdk11/src/main/java/org/eclipse/aether/transport/jdk/JdkTransporter.java#L409 (when there is a status code < 300). Although Maven does not expect a response from a repository PUT request, we should make sure if a response body is sent this is consumed to not lead to dangling connections. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
