Resource interpreted as Other, but passed with the MIME type undefined

I get an error: "The resource is interpreted as" Other ", but is passed with the MIME type undefined." inside developer tools when loading my page. I'm not sure why he does it or how to solve it.

I wonder if anyone has an idea on how to solve this.

Thanks.

+8
html google-chrome
source share
4 answers

If you use Google fonts, this can happen.

Problem Web Inspector does not recognize application/x-font-woff as a valid mime type.

+3
source share

It seems that the problem is with empty image requests, for example.

 <img src="" /> 

or in an external / embedded style sheet

 background:url(); 

They generate an additional request for the current url (or css file) with the wrong mime type (image).

As I found out, the latter disables css real-time editing features for chrome dev tools.

+1
source share
Good question, I saw the same thing. This seems to be a server side issue.

Chrome says, "The resource is interpreted as a script, but wraps with the MIME type text / plain." , what gives?

0
source share

As others have said, this can be caused by several different things, but it never matters as long as your content is displayed well. If not, this is probably a server-side mime type problem, which can be solved by adding a rule to the .htaccess file in Apache.

0
source share

All Articles