Support custom mime types (content-type) #472
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👍 lgtm |
|
Why has this not been merged? Such a simple change which solves so many problems. I'll be hand-copying these changes so I can use http-server to serve wasm modules. |
|
Even with this patch I wasn't able to use wasm modules -- probably due to #480 . As noted there, with ecstatic 4.0.0 wasm was served with the correct content-type out-of-the-box. |
|
Closing in favor of #693, since we'll be able to support it directly |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Just pass the mimeTypes option to node-ecstatic.