Simplify CORS for Minimal APIs

[rafikiassumani-msft]

No description provided.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[praEngineer]

In my VS2022 I have a Blazor WASM. When I start it with IIS Express, it generates a CORS block as it attempts use of the "BrowserLinkSignalR". Nevertheless, I can step through code execution.

However, if I start from the "Browser Link Dashboard" -- "View in Browser" the CORS issue above is not in the browser console log. The unfortunate result is that in this method of running the WASM, I cannot step through code execution.

this is in the IIS Express mode of running the WASM: