You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reading the AWS Documentation, it lists 400 and 408 as transient errors that could potentially be retried. See this link under Retryable.
However the botocoredocumentation does not list these two status codes as retryable. Checking the source for TransientRetryableChecker verifies this fact.
I stumbled upon this 2012 discussion where a user named garnaat, presumably a boto dev, mentioned that at one point, AWS requested retrying on 408 be removed. They suggested if the AWS docs states 408 codes should be retried, then boto should be updated.
I haven't been able to find any further discussion on the subject. Should boto be updated to match the official docs?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Reading the AWS Documentation, it lists 400 and 408 as transient errors that could potentially be retried. See this link under
Retryable
.However the
botocore
documentation does not list these two status codes as retryable. Checking the source forTransientRetryableChecker
verifies this fact.I stumbled upon this 2012 discussion where a user named
garnaat
, presumably a boto dev, mentioned that at one point, AWS requested retrying on 408 be removed. They suggested if the AWS docs states 408 codes should be retried, then boto should be updated.I haven't been able to find any further discussion on the subject. Should boto be updated to match the official docs?
Beta Was this translation helpful? Give feedback.
All reactions