Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix extensions for ecmascript types #20

Merged
merged 1 commit into from
Mar 31, 2019

Conversation

paracycle
Copy link
Contributor

According to RFC4329 both application/ecmascript and text/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 for application/ecmascript and text/ecmascript. This PR fixes that regression.

According to [RFC4329](https://tools.ietf.org/html/rfc4329) both
`application/ecmascript` and `text/ecmascript` are associated with
extension `.es` and not `.js`. The [draft RFC](https://tools.ietf.org/html/draft-bfarias-javascript-mjs-01)
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.
@paracycle
Copy link
Contributor Author

@halostatue I see you were the one who merged #11 that caused the regression. Do you mind taking a look at this PR as well? Thank you!

@halostatue halostatue merged commit 5157a9f into mime-types:master Mar 31, 2019
@halostatue
Copy link
Member

Thanks!

tigefa4u pushed a commit to tigefa4u/gitlabhq that referenced this pull request Jun 17, 2019
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.

None yet

2 participants