rmannibucau commented on PR #408: URL: https://github.com/apache/maven-resolver/pull/408#issuecomment-1896498271
> So the workaround is that if you hit this issue with remote repository "foo", then you can check in .mvn/maven.config that sets proper value for repository "foo" (check the config page diff for new option this PR introduces). But the limit is per connection so a limit per repo is pointless :thinking: > As checked with curl site, the value is usually 100 or 128 or above. Spec mentions 100 but it is the concurrent streams per connection, not the concurrent connections, see why the fix does not help? > OR as you propose, fall back to HTTP/1.1 iF we can't make http2 reliable *by default* - without too much reflection technically speaking - let's ensure the default always works, guess it is the minimum we should provide. As mentionned, perf diff is not key enough for maven to be noticeable so no point defaulting to http2. -- 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]
