Include "Retry-After" in the Response Header when Graph Throttling occurs while moving the files from Sharepoint. #313
Description
Which service(blob, file) does this issue concern?
In case the data movement is triggered from Sharepoint to Blob and the graph call returns throttling exception with status code as 429, graph sends the Response header "retry-after".
https://learn.microsoft.com/en-us/graph/throttling#best-practices-to-handle-throttling
The same header is not passed as the Response Header of data movement library to retry the data movement call after some time.
Which version of the SDK was used?
2.0.4
On which platform were you using? (.Net Framework version or .Net Core version, and OS version)
.Net core
How can the problem be reproduced? It'd be better if the code caused the problem can be shared.
This issue can be reproduced only by throwing throttling exception from Graph call.
What problem was encountered?
Not receiving "retry-after" header as part of response.
Have you found a mitigation/solution?
No