[wtgodbe]

Backport of befb2e9.

The shared IIS WebSocket test application asserted that IHttpMaxRequestBodySizeFeature.MaxRequestBodySize was cleared after upgrading for both hosting models. In-process hosting requires that behavior because its read loop enforces the limit, but out-of-process hosting runs on Kestrel, which does not enforce the limit after upgrade.

Scope the assertion to in-process hosting so the following out-of-process tests do not close the WebSocket prematurely:

• OnStartedCalledForWebSocket
• CanSendAndReceieveData
• WebReadBeforeUpgrade

The same fix was applied directly to #69256 and #69301.

[dotnet-policy-service]

Hi @wtgodbe. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document.
Otherwise, please add tell-mode label.

[Copilot]

🟢 Approval recommended

The hosting-specific assertion change has no unresolved review issues.

Pull request overview

Scopes the WebSocket request-body assertion to IIS in-process hosting, preventing premature closure in out-of-process tests.

Changes:

• Detects in-process hosting via IServerVariablesFeature.
• Retains the assertion only for in-process requests.

File summaries

File	Description
src/Servers/IIS/IIS/test/testassets/InProcessWebSite/Startup.WebSockets.cs	Limits the request-body assertion to in-process hosting.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[dotnet-policy-service]

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no conflicting changes have occurred, please rerun validation before merging. You can do this by leaving an /azp run comment here (requires commit rights), or by simply closing and reopening.