Why does one set the resilience policy to all and not 500 & 503 etc. #2904
Unanswered
SalomonHenke
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Generally wondering and haven't been able to find answers online.
I saw that aspire per default sets the resilience Handler to every request.
In my mind it makes more sense to retry unexpected results and given a 400, 401 or whatever it seems to be that those are expected errors that you wouldn't retry as you are more likely to handle them. So something like this:

It might be faulty logic by me, but in my case i don't (?) want to retry an unauthorized. Instead i would rather refresh the token and then call the original code. I can retry, but same input yields same result in the case of unauthorized, no?
Either way, just wondering and haven't worked with resiliensen in a "real" application. I saw that aspire had the default, so thought someone might know.
Thanks for input in advance :)
Beta Was this translation helpful? Give feedback.
All reactions