WebCmdlets get Retry-After from headers if status code is 429

[sdwheeler]

Prerequisites

• Existing Issue: Search the existing issues for this repository. If there is an issue that fits your needs do not file a new one. Subscribe, react, or comment on that issue instead.
• Descriptive Title: Write the title for this issue as a short synopsis. If possible, provide context. For example, "Document new Get-Foo cmdlet" instead of "New cmdlet."

Summary

If the Status Code is 429 it tries to get the Retry-After property from the headers and use it as WebSession.RetryIntervalInSeconds value.

Details

It appears that the new behavior overrides the value supplied by the user using the RetryIntervalSec parameter.

Articles

• reference/7.4/Microsoft.PowerShell.Utility/Invoke-WebRequest.md
• reference/7.4/Microsoft.PowerShell.Utility/Invoke-RestMethod.md

Related Source Pull Requests

• WebCmdlets get Retry-After from headers if StatusCode is 429 PowerShell/PowerShell#18717

Related Source Issues

• Invoke-RestMethod and Invoke-WebRequest do not respect Retry-After header in 429 responses. PowerShell/PowerShell#13188