Allows setting content type header via middleware #47
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.
Currently the "Content-Type" header is automatically set to the value returned by
mime.getType
.If the "Content-Type" header was already set by a middleware then this header will be overwritten.
Within this change the "Content-Type" header is only set if it is not already defined.
The
getFileContentType
method is added to split Content-Type detection from rendering logic.If the Content-Type can't be detected, then no header is sent.
An example middleware which I use for a website which I migrated from PHP to 11ty: