Fix extensions for ecmascript types #20
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.
According to RFC4329 both
application/ecmascript
andtext/ecmascript
are associated with extension.es
and not.js
. The draft RFC that adds.mjs
support does not change those assignments either.Moreover, according to RFC4329,
application/ecmascript
has stricter processing rules, so applications should not be returning that MIME type for Javascript files without opting in to those stricter rules.PR #11, however, introduced a regression by adding
.js
and.mjs
as extensions forapplication/ecmascript
andtext/ecmascript
. This PR fixes that regression.