[release/9.0] Fix IIS outofprocess to remove WebSocket compression handshake #58931
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.
Backport of #58846 to release/9.0
/cc @BrennanConroy
Fix IIS outofprocess to remove WebSocket compression handshake
Description
Blazor enabled websocket compression by default in some cases. IIS OutOfProcess is a hosting model some customers use and it is not compatible with websocket compression.
Fixes https://github.com/dotnet/AspNetCore-ManualTests/issues/2688
Customer Impact
Using IIS OutOfProcess with Blazor Server-side/Interactive will not work.
Regression?
Regression from 8.0
Risk
Added automated testing and did manual testing. Fix is fairly simple change.
Verification
Packaging changes reviewed?