Use agent
AspNetCore.Docs/.github/agents/whats-new-from-release-notes.agent.md
Parameters for the agent to use for creating the What's New for ASP.NET Core in .NET 11 Preview 4:
VERSION = 11.0
PREVIEW = preview4
SOURCE_REF = https://github.com/dotnet/core/blob/main/release-notes/11.0/preview/preview4/libraries.md#rate-limiting-fixes-for-retryafter-fractional-permits-and-chainedratelimiter
Mode = incremental
Important additional instruction:
The .NET release notes contains this sub subject on Rate-limiting fixes for RetryAfter, fractional permits, and ChainedRateLimiter here:
https://github.com/dotnet/core/blob/main/release-notes/11.0/preview/preview4/libraries.md#rate-limiting-fixes-for-retryafter-fractional-permits-and-chainedratelimiter
Usually the What's New for ASP.NET Core in .NET 11 article would use source text from an ASP.NET Core in .NET 11 release notes. However, in this case the source is from .NET release notes.
It is writen from the point of view of a general .NET fixes, but needs to be rewritten if needed to match the point of view of how it would be used by ASP.NET devleopers.
Scope of content. The release notes section covers three fixes bundled together (RetryAfter, fractional permits, ChainedRateLimiter). For the ASP.NET Core audience, the RetryAfter fix is the most relevant. It directly affects the rate-limiting middleware's Retry-After response header. The fractional permits and ChainedRateLimiter disposal fixes are more general-purpose and less ASP.NET Core-specific.
Framing. The release notes say "If you wire RateLimiter into ASP.NET Core middleware...". That's written from the .NET libraries perspective looking outward. The ASP.NET Core article should frame it from the middleware perspective looking inward, e.g., explaining that the rate-limiting middleware now automatically returns a meaningful Retry-After header.
Associated WorkItem - 578410
Use agent
AspNetCore.Docs/.github/agents/whats-new-from-release-notes.agent.md
Parameters for the agent to use for creating the What's New for ASP.NET Core in .NET 11 Preview 4:
VERSION = 11.0
PREVIEW = preview4
SOURCE_REF = https://github.com/dotnet/core/blob/main/release-notes/11.0/preview/preview4/libraries.md#rate-limiting-fixes-for-retryafter-fractional-permits-and-chainedratelimiter
Mode = incremental
Important additional instruction:
The .NET release notes contains this sub subject on Rate-limiting fixes for RetryAfter, fractional permits, and ChainedRateLimiter here:
https://github.com/dotnet/core/blob/main/release-notes/11.0/preview/preview4/libraries.md#rate-limiting-fixes-for-retryafter-fractional-permits-and-chainedratelimiter
Usually the What's New for ASP.NET Core in .NET 11 article would use source text from an ASP.NET Core in .NET 11 release notes. However, in this case the source is from .NET release notes.
It is writen from the point of view of a general .NET fixes, but needs to be rewritten if needed to match the point of view of how it would be used by ASP.NET devleopers.
Scope of content. The release notes section covers three fixes bundled together (RetryAfter, fractional permits, ChainedRateLimiter). For the ASP.NET Core audience, the RetryAfter fix is the most relevant. It directly affects the rate-limiting middleware's Retry-After response header. The fractional permits and ChainedRateLimiter disposal fixes are more general-purpose and less ASP.NET Core-specific.
Framing. The release notes say "If you wire RateLimiter into ASP.NET Core middleware...". That's written from the .NET libraries perspective looking outward. The ASP.NET Core article should frame it from the middleware perspective looking inward, e.g., explaining that the rate-limiting middleware now automatically returns a meaningful Retry-After header.
Associated WorkItem - 578410