Blazor Server script fallback policy authorization #32035
Merged
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.
Fixes #31931
Thank you @CoskunSunali for that great write-up 🥇. I've combined your remarks with Stephen's response to address this subject in the Migration article. It's here for review if you would like to provide feedback 👂.
Stephen said on the issue ...
... but I think I need a more specific change set to update the article. I'm also not generally clear what "Blazor static files" means ... I don't think he meant that Static File Middleware no-ops in BWAs. I think he means that static assets managed by Blazor (the framework) are now (8.0+) mapped via endpoint routing. Anyway, a specific change set for the article would be helpful. I'd like to knock it out 🤜😵 on this PR if possible. If not tho ... I can open a new issue to address it later.
Internal previews