admin管理员组

文章数量:1127692

Why am I getting this error in console?

Refused to execute script from ';q=flower&searchType=image&fileType=jpg&imgSize=small&alt=json' because its MIME type ('application/json') is not executable, and strict MIME type checking is enabled.

Why am I getting this error in console?

Refused to execute script from 'https://www.googleapis.com/customsearch/v1?key=API_KEY&q=flower&searchType=image&fileType=jpg&imgSize=small&alt=json' because its MIME type ('application/json') is not executable, and strict MIME type checking is enabled.

Share Improve this question edited Nov 13, 2016 at 13:26 George Kagan 6,1148 gold badges49 silver badges50 bronze badges asked Nov 13, 2016 at 13:06 rob.mrob.m 10.6k21 gold badges84 silver badges174 bronze badges 0
Add a comment  | 

33 Answers 33

Reset to default 1 2 Next 184

In my case it was a file not found, I typed the path to the javascript file incorrectly.

You have a <script> element that is trying to load some external JavaScript.

The URL you have given it points to a JSON file and not a JavaScript program.

The server is correctly reporting that it is JSON so the browser is aborting with that error message instead of trying to execute the JSON as JavaScript (which would throw an error).


Odds are that the underlying reason for this is that you are trying to make an Ajax request, have hit a cross origin error and have tried to fix it by telling jQuery that you are using JSONP. This only works if the URL provides JSONP (which is a different subset of JavaScript), which this one doesn't.

The same URL with the additional query string parameter callback=the_name_of_your_callback_function does return JavaScript though.

This result is the first that pops-up in google, and is more broad than what's happening here. The following will apply to an express server:

I was trying to access resources from a nested folder.

Inside index.html i had

<script src="./script.js"></script>

The static route was mounted at :

app.use(express.static(__dirname));

But the script.js is located in the nested folder as in: js/myStaticApp/script.js I just changed the static route to:

app.use(express.static(path.join(__dirname, "js")));

Now it works :)

Try to use express.static() if you are using Node.js.

You simply need to pass the name of the directory where you keep your static assets, to the express.static middleware to start serving the files directly. For example, if you keep your images, CSS, and JavaScript files in a directory named public, you can do as below −

i.e. : app.use(express.static('public'));

This approach resolved my issue.

In my case, I was working on legacy code

and I have this line of code

<script type="text/javascript" src="js/i18n.js.php"></script>

I was confused about how this supposed to work this code was calling PHP file not js

despite it was working on the live server

but I have this error on the stage sever

and the content type was

content-type: text/html; charset=UTF-8

even it is text/javascript in the script tag

and after I added

header('Content-Type: text/javascript');

at the beginning for file i18n.js.php

the error is fixed

After searching for a while I realized that this error in my Windows 10 64 bits was related to JavaScript. In order to see this go to your browser DevTools and confirm that first. In my case it shows an error like "MIME type ('application/javascript') is not executable".

If that is the case I've found a solution. Here's the deal:

  1. Borrowing user "ilango100" on https://github.com/jupyterlab/jupyterlab/issues/6098:

I had the exact same issue a while ago. I think this issue is specific to Windows. It is due to the wrong MIME type being set in Windows registry for javascript files. I solved the issue by editing the Windows registry with correct content type:

regedit -> HKEY_LOCAL_MACHINE\Software\Classes -> You will see lot of folders for each file extension -> Just scroll down to ".js" registry and select it -> On the right, if the "Content Type" value is other than application/javascript, then this is causing the problem. Right click on Content Type and change the value to application/javascript

Try again in the browser."

After that I've realized that the error changes. It doesn't even open automatically in the browser anymore. PGAdmin, however, will be open on the side bar (close to the calendar/clock). By trying to open in the browser directly ("New PGAdmin 4 window...") it doesn't work either.

FINAL SOLUTION: click on "Copy server URL" and paste it on your browser. It worked for me!

EDIT: Copying server URL might not be necessary, as explained by Eric Mutta in the comment below.

I accidentally named the js file .min instead of .min.js ...

Python flask

On Windows, it uses data from the registry, so if the "Content Type" value in HKCR/.js is not set to the proper MIME type it can cause your problem.

Open regedit and go to the HKEY_CLASSES_ROOT make sure the key .js/Content Type has the value text/javascript

C:\>reg query HKCR\.js /v "Content Type"

HKEY_CLASSES_ROOT\.js
    Content Type    REG_SZ    text/javascript

In my case (React app), just force cleaning the cache and it worked.

I had my web server returning:

Content-Type: application\javascript

and couldn't for the life of me figure out what was wrong. Then I realized I had the slash in the wrong direction. It should be:

Content-Type: application/javascript

In my case, while executing my typescript file, I wrote:

<script src="./script.ts"></script>

Instead of:

<script src="./script.js"></script>

In my case Spring Security was looking for authentication before allowing calls to external libraries. I had a folder /dist/.. that I had added to the project, once I added the folder to the ignore list in my WebSecurityConfig class, it worked fine.

web.ignoring().antMatchers("/resources/**", "/static/**", "/css/**", "/js/**", "/images/**", "/error", "/dist/**");

You can use just use type:

<script type='text/javascript' src="fileType.js"></script>

or whichever type you're using, you choose that file type.

In my case, I wrote:

<script src="./script.js"></script>

Instead of:

<script src="/script.js"></script>

I was adding a dot at starting of path which was my mistake.

Check for empty src in script tag.

In my case, i was dynamically populating src from script (php in my case), but in a particular case src remained empty, which caused this error.

Like this:

 <script src=""></script> //empty src causes error

So instead of empty src in script tag, I removed the script tag all together.

Like this:

if($src !== ''){
    echo '<script src="'.$src.'"></script>';
}

My problem was that I have been putting the CSS files in the scripts definition area just above the end of the Try to check the files spots within your pages

I am using SpringMVC+tomcat+React

@Anfuca's answer does not work for me(force cleaning the browser's cache)

I used Filter to forward specific url pattern to the React's index.html

public class FrontFilter extends HttpFilter {
    @Override
    protected void doFilter(HttpServletRequest req, HttpServletResponse res, FilterChain chain) throws IOException, ServletException {
        boolean startsWithApi = requestURI.startsWith("/api/");
        boolean isFrontendUri = requestURI.startsWith("/index.html");

        if (!startsWithApi && !isFrontendUri) {
            req.getRequestDispatcher("/index.html").forward(req, res);
        }

        super.doFilter(wrapped, res, chain);
    }
}

There is no Spring Security problem bcs my filter executes before Spring Security's

but I still see the same error and find here

Then I realized that I forgot adding one more condition for JS and CSS:

boolean startsWithStatic = requestURI.startsWith(contextPath + "/static");

Add this to my if condition and problem solved, no more error with MIME type or ('text/html') with js and css

Root cause is that I incorrectly forward JS and CSS type to HTML type

In my case, there was no code change nor deployment and it was actually accessible a day before yet im seeing this issue.

I resolved this by clearing my browser data for the past 24hours.

Particular case with Cloudfront distribution.

I was serving a umd.cjs file as a CDN, and got the error:

The resource from “https://your.distribution.com/library.umd.cjs” was blocked due to MIME type (“binary/octet-stream”) mismatch (X-Content-Type-Options: nosniff).

I was saving a .js library in a S3 bucket but because of the extension umd.cjs the S3 tagged the file as binary, so I had to change the metadata of this file manually and set the content-type to "application/javascript"

If you have a particular case as me, try to find any useful or extra metadata that you can configure in your service providers.

After a npm run build I tried to open the Index.html file locally and got the error in title. I tried using Live Server and found the paths to resources were incorrect.

To work around this I used http-server to run the app locally:

Install http-server globally if you haven't already:

npm install -g http-server

Navigate to your build folder:

cd your/build/folder

Start the server:

http-server

It will prompt you to open localhost:8080

I got the same error. I realized my app.js was in another folder.

I just moved it into that folder where my index.html file is and it resolved.

In my case, I was getting the same error when running:

 node server.js

but when I run:

 npm start

the error disappeared and everything worked as expected. Here is my project structure:

Root_directory with

public and server as sub-folders,

under the public folder, I have two files: app.js and index.html , and under the server folder I have only one file which is the server.js

I had the same problem, In my case the solution was completely different. It seems that when you have the HtmlWebpackPlugin you should not set the src tag of your script element with the path of your js file but you should just specify the type tag.

Add the code snippet as shown below to the entry html. i.e "index.html" in reactjs

<div id="wrapper"></div>
<base href="/" />

If you have a route on express such as:

app.get("*", (req, res) => {
  ...
});

Try to change it for something more specific:

app.get("/", (req, res) => {
  ...
});

For example.

Or else you just might find yourself recursively serving the same HTML template over and over...

In my case I had a symlink for the 404'd file and my Tomcat was not configured to allow symlinks.

I know that it is not likely to be the cause for most people, but if you are desperate, check this possibility just in case.

In Angular Development try this

In my case that script file has wrong suffix name. I used script.min.js instead of script.js.min

Just try with CTRL+F5, helped in my case. It's probably a cache problem.

In my situation in was because its MIME type ('application/html') is not executable, and strict MIME type checking is enabled was the error from GoDaddy using Bridge Theme with QI Slider loading Bootstrap: carousel.js v3.0.0 and was missing transitions.js.

Add CDN from cloudflare transition.js v3.2.0.

CDN is here:

https://www.cdnpkg.com/twitter-bootstrap/file/transition.js

本文标签: javascriptRefused to execute scriptstrict MIME type checking is enabledStack Overflow