#12556 Implement adaptive request throttling on HTTP 429 (Too Many Requests) responses#12587
Open
Binabh wants to merge 2 commits into
Open
#12556 Implement adaptive request throttling on HTTP 429 (Too Many Requests) responses#12587Binabh wants to merge 2 commits into
Binabh wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
RateLimitManagerand using it in axios interceptorsloadFunctionand also for cesiumPlease check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#12556
What is the new behavior?
Mapstore correctly reads Retry-After header in case of 429 response and handles accordingly.
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information
To test all of the features implemented just having a running Geoserver may not be enough. For testing purpose we can start a simple proxy server in front of Geoserver to apply rate limits. Python proxy server used:
rate_limit_server.py