jiteshkhatri11 commented on issue #2151: URL: https://github.com/apache/maven-resolver/issues/2151#issuecomment-6315276538
Thanks for investigating this, @ahus1, and for sharing these real-world CI examples. It sounds like the existing retry handler already covers much of the proposed functionality, including I/O retries, backoff, and `Retry-After` support. The default handling of HTTP 502 and 504 appears to be a more specific gap worth addressing first. I agree that treating 502 and 504 as retryable by default could improve CI reliability while preserving the existing behavior for permanent errors such as 401, 403, and 404. I'd be happy to investigate the current implementation and tests to identify the smallest backward-compatible change, including whether the default status-code list can be extended without affecting other transport behavior. -- 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]
