Skip to content

Remove .wasm file extension before redefining it#24950

Merged
guardrex merged 1 commit intodotnet:mainfrom
campersau:patch-1
Feb 9, 2022
Merged

Remove .wasm file extension before redefining it#24950
guardrex merged 1 commit intodotnet:mainfrom
campersau:patch-1

Conversation

@campersau
Copy link
Copy Markdown
Contributor

I had to remove the .wasm file extension because IIS was complaining about duplicate entries in order to make it work with br and https.

Others also reported this issue on stackoverflow:
https://stackoverflow.com/a/69888016
https://stackoverflow.com/a/70967738

@guardrex guardrex self-assigned this Feb 9, 2022
Copy link
Copy Markdown
Collaborator

@guardrex guardrex left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @campersau 🚀 ... and note that this whole node of topics (Host and Deploy) is due for an overhaul and series of updates per #24615. I've cross-linked the tracking issue to this PR and to the SO posts that you mentioned for when I test and improve the guidance.

I think one of the things that I'll do where it tells readers that the example web.config file is a starting point for further customization is to call out our list of recommended public support channels (SO, Slack, Gitter). I'll probably include a tag filter in the SO link (https://stackoverflow.com/questions/tagged/blazor+iis+compression).

Thanks for sending this PR.

@guardrex guardrex merged commit 1c6f5c4 into dotnet:main Feb 9, 2022
@campersau campersau deleted the patch-1 branch February 9, 2022 13:00
@guardrex guardrex mentioned this pull request Jan 3, 2025
96 tasks
@guardrex guardrex mentioned this pull request Feb 6, 2026
67 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants