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

Use text/javascript, not application/javascript, for .js #151

Closed
laukstein opened this issue Jan 9, 2019 · 1 comment
Closed

Use text/javascript, not application/javascript, for .js #151

laukstein opened this issue Jan 9, 2019 · 1 comment

Comments

@laukstein
Copy link

Issue mentioned in github/pages-gem#612

See webhintio/hint#568 (comment),
https://html.spec.whatwg.org/multipage/scripting.html#scriptingLanguages says:

Servers should use text/javascript for JavaScript resources. Servers should not use other JavaScript MIME types for JavaScript resources, and must not use non-JavaScript MIME types.

https://html.spec.whatwg.org/multipage/infrastructure.html#dependencies says:

35584113-dd11f0f6-05a8-11e8-9939-4ad4c85dab3f

@dougwilson
Copy link
Contributor

Hi @laukstein ! Our mappings come from the three sources listed at the top of the README. This module just aggregates the sources into a JSON database.

The particular mapping you're referring to (application/javascript -> js) in our database is coming from two sources: the NGINX project and the Apache HTTPD project.

NGINX: http://hg.nginx.org/nginx/raw-file/default/conf/mime.types
Apache HTTPD: http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types

If these projects have the incorrect mapping, you'll need to raise the issue in these projects, and once they update their mappings, the updates will automatically be pulled into this database.

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

No branches or pull requests

2 participants