CSS file blocked: MIME type mismatch (X-Content-Type-Options: nosniff)

Cssnode.jsAngularExpressMime Types

Css Problem Overview


I am developing an Angular 4 app and I want to apply some global styles. Following the tutorial at the angular site, I've created a "styles.css" file in the root directory of my app, and I'm referring to that stylesheet in the index.html of my app:

<link rel="stylesheet" type="text/css" href="styles.css">

The angular app is successfully compiled:

$ ng serve 
** NG Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200 **
[...]
webpack: Compiled successfully.

But when I visit http://localhost:4200 in a Chromium browser, the console shows an error at

GET http://localhost:4200/styles.css 

In a Firefox browser, the error is a bit more explicit:

GET 
http://localhost:4200/styles.css [HTTP/1.1 404 Not Found 15ms]
The resource from "http://localhost:4200/styles.css" was blocked due to MIME type mismatch (X-Content-Type-Options: nosniff).

Both files, index.html and styles.css are located in the root directory of my angular app. I've tried to get more info about the problem :

nosniff
    Blocks a request if the requested type is

        "style" and the MIME type is not "text/css", or
        "script" and the MIME type is not a JavaScript MIME type.

But I don't understand why it's bloking the request, since I've specified type="text/css" when referencing the stylesheet.

Css Solutions


Solution 1 - Css

I just ran into the same issue. It appears to be a quirk of Express that can manifest itself for a few different reasons, judging by the number of hits from searching the web for "nodejs express css mime type".

Despite the type="text/css" attribute we put in our <link elements, Express is returning the CSS file as

Content-Type: "text/html; charset=utf-8"

whereas it really should be returning it as

Content-Type: "text/css"

For me, the quick and dirty workaround was to simply remove the rel= attribute, i.e., change

<link rel="stylesheet" type="text/css" href="styles.css">

to

<link type="text/css" href="styles.css">

Testing confirmed that the CSS file was downloaded and the styles did actually work, and that was good enough for my purposes.

Solution 2 - Css

I also removed rel = "stylesheet", and I no longer get the MIME type error, but the styles are not being loaded

Solution 3 - Css

Some answers suggested removing rel="stylesheet", that didn't work out for me however. According to the expressjs documentation: https://expressjs.com/en/starter/static-files.html use express.static function to serve static files such as CSS, JavaScript,etc...

app.use(express.static('public'))

and from there you should be able to load any file under the public directory for example, if you have a style.css file inside the directory {PROJECT_PATH}/public/css/

http://localhost:3000/css/style.css will work.

Solution 4 - Css

In running into the same kind of issue for a full stack web application (in development), I simply solved the problem by correctly linking the css file to the page rendered. Removing the rel = stylesheet, as suggested above, prevents the error to show up in the browser but it does not load the styles that should be applied to the page. In short, it isn't a solution.

If you are using express-static you can use this as an example:

Server-side:

app.use(express.static(__dirname + "/public", {
    index: false, 
    immutable: true, 
    cacheControl: true,
    maxAge: "30d"
}));

Client-side:

 <link type="text/css" rel="stylesheet" href="/main.css">

Just add a forward slash in front of the file you wish to link to the html page (if you are rendering html pages without using any template engines) and express-static will do the rest automatically for you.

Solution 5 - Css

Had a similar problem with a javascript file (as opposed to css) in an Angular app. In reality, the problem wasn't with the Mime type (as the outer error message indicated) but was ultimately a "404 Not Found" error.

In my case, putting the script file anywhere but in the "assets" folder resulted in the 404 and eventually the mime type error. The following tag worked for me in the head section of index.html:

<script src="assets/plugins/jquery.min.js" type="text/javascript"></script>

The assets folder is a sibling of the Index.html file.

Solution 6 - Css

This is solved my problem:

app.use('/public', express.static(path.join(__dirname, "public")));

Solution 7 - Css

A simple hack is to add a forward slash / before the the path to the stylesheet used. For me it was href='css/style.css', changed it to href='/css/style.css'. Worked like a charm.

Solution 8 - Css

I also had this issue.

I moved the script file to a different location and now there is no error:

from <script src="./scripts/simple-keyboard/keyboard.index.min.js" type="text/html"></script>
to <script src="./scripts/keyboard.index.min.js" type="text/javascript"></script>

As noted by Davelli, the issue wasn't a file mismatch but an error not found. It's strange it returned the wrong error!

Solution 9 - Css

if this solutions does not help:

 app.use(express.static('public'))//for server
<link rel="stylesheet" href="/index.css">//for styles

Then make sure that "public" folder exists in the root directory. This was my case.

Solution 10 - Css

I was facing the same problem. But I found out that it has to do with using the right directory for your style.css file. So I tried this line of code below and it worked perfectly.

<link rel="stylesheet" type="text/css" href="/app/scss/style.css">

Solution 11 - Css

What seemed to work for me was changing

<script type="text/javascript" src="/lib/matrix.js"></script>

to

<script type="text/javascript" src="./lib/matrix.js"></script>

Solution 12 - Css

I ran into this problem as well. I was able to fix the problem with the tip from Kirankumar Gonti.

Use the following line:

app.use('/public', express.static(path.join(__dirname, "public")));

Make sure to set the const path.

You also want to make sure your css folder is nested inside a public folder.

Solution 13 - Css

I ran into this problem as well. I was able to fix the problem with the tip from Kirankumar Gonti.

I used the following line of code in my app.js file, I didn't have a public folder but had my style.css stored in a css folder:

app.use('/css', express.static(path.join(__dirname, "css")));

In my /css/style.css file I used:

<link rel="stylesheet" type="text/css" href="/css/style.css" />

Solution 14 - Css

For anyone still having this error I was able to solve it by including "src/assets" in my angular.json file

"assets": ["src/favicon.ico", "src/assets", "src/upload.php"]

also the directory of your index.html should not be included in the assets. meaning you should not include "src" in "assets"

Solution 15 - Css

In my case I had jumbled up the code blocks below in reverse order so I was getting this error. If you have this issue, follow the below order and it might help

 app.use(express.static(path.join(__dirname, 'public')));
app.get('*', (req, res) => {
   res.sendFile(path.join(__dirname, 'public/index.html'));
});

3.

app.use('/api', cors(corsOptions), indexRouter);

Solution 16 - Css

This is what happened at me, My site was archieved, so the css and js files are not available. After restore my webhost everything goes well.

So, please check are the URLs is correct or not.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionrodrunnerView Question on Stackoverflow
Solution 1 - CssGord ThompsonView Answer on Stackoverflow
Solution 2 - CssFer CervantesView Answer on Stackoverflow
Solution 3 - CssmotashView Answer on Stackoverflow
Solution 4 - Cssrags2riches-progView Answer on Stackoverflow
Solution 5 - CssDaveIIiView Answer on Stackoverflow
Solution 6 - CssKirankumar GontiView Answer on Stackoverflow
Solution 7 - CssAkash RanaView Answer on Stackoverflow
Solution 8 - CssimatworkView Answer on Stackoverflow
Solution 9 - CssM22View Answer on Stackoverflow
Solution 10 - CssSLYHUNTERXView Answer on Stackoverflow
Solution 11 - CssΝίκος ΔημητρακόπουλοςView Answer on Stackoverflow
Solution 12 - CssvjstereoView Answer on Stackoverflow
Solution 13 - CssCharlie MacView Answer on Stackoverflow
Solution 14 - CssAbiola AribisalaView Answer on Stackoverflow
Solution 15 - CssSupradeepView Answer on Stackoverflow
Solution 16 - CsstohaView Answer on Stackoverflow