Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Client throttling is supported in Public Client Application #159

Closed
henrik-me opened this issue Feb 12, 2020 · 0 comments · Fixed by #379
Closed

[Feature Request] Client throttling is supported in Public Client Application #159

henrik-me opened this issue Feb 12, 2020 · 0 comments · Fixed by #379

Comments

@henrik-me
Copy link

Overview

  • Blocking request after receiving 429, 5xx HTTP status.
  • Respecting Retry-After header on any HTTP response.
  • Cache for responses of interaction required messages.

Important
It is expectation that the calling application behavior should not change by this features, as well as it is not expected the increase of number of prompts.

Note:
This effort is related to Public Client applications only.

Related docs:
Epic 328219: Client throttling is supported in MSAL & Brokers
Design

@navyasric navyasric added this to To do in MSAL Python Board Apr 21, 2020
@navyasric navyasric moved this from To do to In progress in MSAL Python Board Apr 21, 2020
@rayluo rayluo moved this from In progress to To do in MSAL Python Board Aug 25, 2020
@navyasric navyasric moved this from To do (this release) to Todo (This Quarter) in MSAL Python Board Jan 14, 2021
@henrik-me henrik-me added this to the FY21Q3 milestone Jan 15, 2021
@henrik-me henrik-me removed this from the FY21Q3 milestone May 4, 2021
@rayluo rayluo moved this from Todo (This Quarter) to In progress in MSAL Python Board Jun 10, 2021
@rayluo rayluo mentioned this issue Jul 8, 2021
MSAL Python Board automation moved this from In progress to Done Aug 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants