Update API Rate Limit Headers to reflect IETF Proposal #25269
Merged
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.
Summary
The underlying services were updated one to two weeks ago to use the IETF proposed
RatelimitandRatelimit-Policyheaders. This change updates the relevant Changelog announcing the new headers and the Fundamentals section to more accurately reflect the response headers that relate to rate limiting.Full draft IETF proposal: https://ietf-wg-httpapi.github.io/ratelimit-headers/draft-ietf-httpapi-ratelimit-headers.html#name-introduction
Screenshots (optional)
N/A
Documentation checklist
N/A