You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
The text was updated successfully, but these errors were encountered:
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
Subscription Level Throttling
Burst Control Level Throttling
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
The text was updated successfully, but these errors were encountered: