NetBurner Community Forum

Hi Everyone,

I am using the SB70LC Rev1.5 embedded webserver (PINK). I designed a webpage and tried opening is up
in IE10, but I get some messages:

Resource interpreted as Stylesheet but transferred with MIME type text/plain: "http://192.168.2.220/jquery-ui-1.10.3.custom.min.css". index.html:9

Resource interpreted as Script but transferred with MIME type text/plain: "http://192.168.2.220/jquery-ui-1.10.3.custom.min.js". index.html:11

Resource interpreted as Script but transferred with MIME type text/plain: "http://192.168.2.220/Ajax_Query.js". index.html:28

Resource interpreted as Script but transferred with MIME type text/plain: "http://192.168.2.220/Ajax_Tabs.js". index.html:29

Resource interpreted as Script but transferred with MIME type text/plain: "http://192.168.2.220/Ajax_Submit.js". index.html:30

Resource interpreted as Script but transferred with MIME type text/plain: "http://192.168.2.220/jquery-1.10.2.min.js". index.html:10

I posted this on the jQuery newsgroups and someone said that the server wasn't setting up the MIME types correctly?
Has anyone come across this?

Thanks.

Hello,

Can you try loading the lastest application image, located at
http://www.netburner.com/support/docume ... /855-50-16

When I look at the current MIME settings, it appears to be correct fos .js and .css:

.css 1 text/css
.js 1 text/javascript

Hi Forrest,

I updated with SB70LC-PinkApp-R1p37-20120216_APP.s19, I am getting the following warning from the
console using (IE10 debug tool).

SEC7113: CSS was ignored due to mime type mismatch
File: jquery-ui-1.10.3.custom.min.css


I looked up what this meant:

SEC7113

"CSS was ignored due to mime type mismatch"

An imported style sheet was not used due to the wrong MIME type in the HTTP header.

Ensure style sheet file is delivered with the proper HTTP response header, which includes a content type of text\css. See MIME-Handling Changes in Internet Explorer for more information.

It can be seen here:
http://msdn.microsoft.com/en-us/library ... s.85).aspx

At least I am getting less, but this one still resides... is it something that you can address?

Thank you,
Neil