You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2019/10/17 01:06:16 UTC

[GitHub] [maven-wagon] zymzxq commented on issue #57: WAGON-567: support retry on server side errors

zymzxq commented on issue #57: WAGON-567: support retry on server side errors
URL: https://github.com/apache/maven-wagon/pull/57#issuecomment-542952547
 
 
   Agree >=500 is too coarse grained. I'd also like to check 500 and 502 as well. AWS s3, which we redirect our maven download requests to,  returns 500 when it has problems and expects client to retry. We also experienced s3 returned 502 when it had issues. AWS document: https://stash.atlassian.com/projects/BUILDENG/repos/buildeng-plan-templates/pull-requests/1024/overview
   
   Happy to remove the non standard 420 check.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services