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

The content-type 'application/javascript' should not raise an error #525

Closed
Pamplemousse opened this issue Oct 2, 2018 · 1 comment
Closed

Comments

@Pamplemousse
Copy link

I get an error in the Interoperability section during the scan of a website, stating:

'content-type' header media type value should be 'text/javascript', not 'application/javascript'. 

Hinting that the text/javascript should be used in place of the application/javascript.

However, this is the exact opposite of what the RFC 4329 states:

   Use of the "text" top-level type for this kind of content is known to
   be problematic.  This document thus defines text/javascript and text/
   ecmascript but marks them as "obsolete".  Use of experimental and
   unregistered media types, as listed in part above, is discouraged.
   The media types,

      * application/javascript
      * application/ecmascript

   which are also defined in this document, are intended for common use
   and should be used instead.
@alrra
Copy link
Contributor

alrra commented Oct 2, 2018

@Pamplemousse See webhintio/hint#568 (comment). Thanks!

@alrra alrra closed this as completed Oct 2, 2018
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