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
[core] Retry on 503 using the Retry-After header (Azure#15906)
Based on the Retry-After specification, 503 should also be supported when considering the Retry-After header.
This also aligns with upcoming Identity plans.
Copy file name to clipboardExpand all lines: sdk/core/core-rest-pipeline/CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,12 @@
6
6
7
7
- Fixed an issue where `proxySettings` does not work when there is username but no password [Issue 15720](https://github.com/Azure/azure-sdk-for-js/issues/15720)
8
8
9
+
### Features Added
10
+
11
+
- Added support for the `Retry-After` header on responses with status code 503, Service Unavailable.
12
+
- The `ExponentialRetryPolicy` will now ignore `503` responses if they have the `Retry-After` header.
13
+
- Added support for multiple retries on the `ThrottlingRetryPolicy` (up to 3 by default).
14
+
9
15
### Breaking Changes
10
16
11
17
- Updated @azure/core-tracing to version `1.0.0-preview.12`. See [@azure/core-tracing CHANGELOG](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/core/core-tracing/CHANGELOG.md) for details about breaking changes with tracing.
0 commit comments