Add rate-limiting RetryAfter fixes to What's New for .NET 11 Preview 4#37151
Conversation
Agent-Logs-Url: https://github.com/dotnet/AspNetCore.Docs/sessions/ff6f5db4-b8a9-4897-bae7-31d2ce227450 Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com>
|
@copilot, Check against the code sample used in the source release notes content here: Determine why the code example was not included here in the PR, and fix if needed. |
Agent-Logs-Url: https://github.com/dotnet/AspNetCore.Docs/sessions/ec595e41-7255-4739-a28b-d3514c2caf95 Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com>
The code sample was omitted in the initial commit because I focused on reframing the prose for the ASP.NET Core audience and didn't carry over the code block. Added it now in commit 1eddbe7 — it shows how a |
|
Just spotted that I need to adress the cross-link warning from the build: Switching it to code ticks for now. The API ref is not available yet. |
Removing cross-link until <xref:System.Threading.RateLimiting.ChainedRateLimiter%601> is avaialble in API ref build.
Removing code snippet per review suggestion. It is not relevant to the ASP.NET Core rate limiting middleware scenario.
|
@copilot, rename this include file from rate-limiting-retry-after-preview4.md to rate-limiting-retry-after-preview-4.md |
…ate reference Agent-Logs-Url: https://github.com/dotnet/AspNetCore.Docs/sessions/4542cc0b-fadf-40e6-8735-4156936fe239 Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com>
|
Thanks @danroth27 for the suggested changes. Those are all in now. |
Co-authored-by: Daniel Roth <daroth@microsoft.com>
Fix per gewarren review suggestion.
Fixes #37150 (Detailed instrucions + parameters were provided there for our custom agent for this repo)
Adds coverage of the
System.Threading.RateLimitingfixes from the .NET 11 Preview 4 libraries release notes, reframed for the ASP.NET Core audience.The source material in
dotnet/coreis written from the .NET libraries perspective. The include file reframes it from the middleware perspective:RetryAfter— the most relevant fix for ASP.NET Core developers.FixedWindowRateLimiternow reports accurateRetryAftermetadata, so the rate-limiting middleware automatically sets a meaningfulRetry-Afterresponse header.TokenBucketRateLimiterfractional permits andChainedRateLimiterforwarding fixes.Changes
aspnetcore/release-notes/aspnetcore-11/includes/rate-limiting-retry-after-preview4.mdaspnetcore/release-notes/aspnetcore-11.md— added[!INCLUDE]in Miscellaneous section, updatedms.dateInternal previews