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
I was surprised to see no mention of the handling of retry-after header by the client.
I had to look at the code to find the above code snippet.
This behavior is not documented in the RetryDelay option that can be set on the clients:
// RetryDelay specifies the initial amount of delay to use before retrying an operation.
// The delay increases exponentially with each retry up to the maximum specified by MaxRetryDelay.
// The default value is four seconds. A value less than zero means no delay between retries.
RetryDelay time.Duration
The text was updated successfully, but these errors were encountered:
ghost
added
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Jul 20, 2022
serbrech
changed the title
azcore/policy retry: missing documentation of handling of retry-after header
azcore/policy retry: missing documentation about handling of retry-after header
Jul 20, 2022
azure-sdk-for-go/sdk/azcore/runtime/policy_retry.go
Lines 173 to 177 in b386adc
I was surprised to see no mention of the handling of retry-after header by the client.
I had to look at the code to find the above code snippet.
This behavior is not documented in the RetryDelay option that can be set on the clients:
azure-sdk-for-go/sdk/azcore/policy/policy.go
Lines 84 to 87 in b386adc
The text was updated successfully, but these errors were encountered: