Improve default RetryHandler implementation

[Geiste]

Is your feature request related to a problem? Please describe the problem.

SDK V5
As per incident: 2409111420000033
in case there is a low memory on server side the server returns 503 for other error codes.

In such cases SDK treats 404, 403 errors as if it is 503 and retries.

We were instructed by Microsoft support person of contact to implement RetryHandler on application side and retry only if "retry-after" header is present. However, it sounds like this should be handled in SDK side rather than us.

Describe the solution you'd like.

I would propose such cases, when Microsoft servers have low memory to be handled by SDK

Additional context?

No response

[Ndiritu]

Hi @Geiste, are you referencing an IcM incident number? I'm unable to find one with that number.
Please share a link.

Unfortunately we are currently only doing security patches for v5 and would recommend you upgrade to v6 of the SDK which correctly handles retries

[Geiste]

Hi, Thank you for your answer. We are currently upgrading to v6 and will finalize soon, so if retries are handled correctly in that version then its fine. Thank you :)

…

On Tue, 8 Oct 2024 at 03:18, Philip Gichuhi ***@***.***> wrote: Hi @Geiste <https://github.com/Geiste>, are you referencing an IcM incident number? I'm unable to find one with that number. Please share a link. Unfortunately we are currently only doing security patches for v5 and would recommend you upgrade to v6 of the SDK which correctly handles retries — Reply to this email directly, view it on GitHub <#2186 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH3BE4RLEWCUAPMC5PG2FGLZ2MQENAVCNFSM6AAAAABPPCEPTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJYGI3DAOJZHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>