Document MinResponseDataRate transport buffer limitation

[Copilot]

Document MinResponseDataRate transport buffer limitation

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Clarify MinResponseDataRate behavior regarding OS buffer mechanics

Description

MinResponseDataRate measures data written from the server's perspective, not actual client consumption. Added remarks to XML documentation explaining that the rate may not accurately reflect how much data a client is reading because the transport reads data until OS buffers are full.

Updated locations:

• KestrelServerLimits.MinResponseDataRate property
• IHttpMinResponseDataRateFeature.MinDataRate property

This clarifies expected behavior when diagnosing slow client scenarios where OS buffers mask the actual consumption rate.

Original prompt

Update MinResponseDataRate XML documentation with a remark that MinResponseDataRate may not accurately measure how much data a client is reading. This is because data is read from the transport until the transport's operating system buffers are full.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[dotnet-policy-service]

Greetings! You've submitted a PR that modifies code that is shared with https://github.com/dotnet/runtime . Please make sure you synchronize this code with the changes in that repo!

[Copilot]

Pull request overview

This PR adds documentation to clarify a key limitation of the MinResponseDataRate feature in Kestrel. The feature measures data written from the server's perspective, not actual client consumption, because the transport reads data from the application until OS buffers are full. This clarification helps developers understand why the rate may not accurately reflect client read behavior when diagnosing slow client scenarios.

Key Changes:

• Added XML documentation remarks explaining the OS buffer limitation to KestrelServerLimits.MinResponseDataRate
• Added identical documentation to IHttpMinResponseDataRateFeature.MinDataRate for consistency

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/Servers/Kestrel/Core/src/KestrelServerLimits.cs	Added paragraph in remarks section explaining that MinResponseDataRate may not accurately measure client read rate due to OS buffer behavior
src/Servers/Kestrel/Core/src/Features/IHttpMinResponseDataRateFeature.cs	Added remarks section with the same OS buffer limitation explanation for the per-request feature interface