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

Retry-After header is not available for burst control throttled responses [APIM 4.0.0] #3128

Closed
Sumudu-Sahan opened this issue Sep 26, 2024 · 1 comment

Comments

@Sumudu-Sahan
Copy link

Description

Retry-After header is not available for burst control throttled responses. But the same header will appear if the throttling is happening at the subscription throttling level.

Steps to Reproduce

  • Start the APIM pack and go to the admin portal.
  • Create 2 new subscription policies (BURSTPOLICY, SUBPOLICY) with below values.
BURSTPOLICY
- Subscription Rate Limit: 10000 requests per 1 minute.
- Burst Rate Limit: 1 request per 1 minute.

SUBPOLICY
- Subscription Rate Limit: 1 request per 1 minute.
- Burst Rate Limit: not configured
  • Go to the publisher portal and create an API.
  • Under the Subscriptions section, enable both subscription policies.
  • Go to the devportal and do 2 tests under the below scenarios.

Subscription Level Throttling

  • Subscribe to the API with an application by using the SUBPOLICY.
  • Invoke the API until it gets throttled out.
  • Check the response headers and able to notice that the Retry-After header is there as below.
1

Burst Control Level Throttling

  • Subscribe to the API with an application by using the BURSTPOLICY.
  • Invoke the API until it got throttled out.
  • Check the response headers and able to notice that the Retry-After header is not there as below.
2

Affected Component

APIM

Version

4.0.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response

@nisan-abeywickrama
Copy link

Closing this issue as the related PR is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants