This is a migrated thread and some comments may be shown as answers.

[Solved] IE9, CSS and webAssets SEC7113

6 Answers 84 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
Joshua
Top achievements
Rank 2
Joshua asked on 20 Nov 2010, 11:00 PM
OK, don't know if anyone is experiencing this yet?  maybe it's just one of my files?

I just installed IE9 beta and when testing my sites the CSS does not load from the handler.  (asset.axd?id=css)

And I get the following message.
"SEC7113: CSS was ignored due to mime type mismatch"

I have my stylesheets in a webAsset group and have them combined.

Does this mean I have to link my stylesheets 'old school'?

thanks in advance.

6 Answers, 1 is accepted

Sort by
0
T. Tsonev
Telerik team
answered on 22 Nov 2010, 12:15 PM
Hi Joshua,

I've verified that the Content-Type is set by WebAssetHttpHandler. This can be seen with Firebug, Fiddler or other debugging tool.



I'm attaching you the project that I've used for testing so you can verify my results.

I've also tested with IE9 Beta and IE Platform Preview 7 and the styles were loaded properly. Are you accessing the site directly or through a proxy / firewall?

Regards,
Tsvetomir Tsonev
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
0
Joshua
Top achievements
Rank 2
answered on 23 Nov 2010, 09:56 PM
In the project you sent you did not combine all CSS files into a group in the web.config

<telerik>
   <webAssets>
      <styleSheets>
         <add name="a" combined="True">
            <items>
               <add source="telerik.common.css"/>
               <add source="telerik.black.css"/>
               <add source="~/Content/style1.css"/>
               <add source="~/Content/style2.css"/>
               <add source="~/Content/style3.css"/>
            </items>
        </styleSheets>
     </webAssets>
</telerik>


I reference multiple files and combine them.  I followed the documentation exactly and get the SEC7113 error with IE9.

can you replicate this?
0
T. Tsonev
Telerik team
answered on 24 Nov 2010, 09:47 AM
Hi Joshua,

Thank you for the additional details. I've managed to reproduce the problem. It's already fixed in the latest internal build that will be uploaded in a few minutes (version 2010.3.1123).

Greetings,
Tsvetomir Tsonev
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
0
T. Tsonev
Telerik team
answered on 24 Nov 2010, 09:52 AM
Hi Joshua,

I'm attaching the hotfix here.

All the best,
Tsvetomir Tsonev
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
0
Joshua
Top achievements
Rank 2
answered on 27 Nov 2010, 06:38 PM
You guys are awesome!!  Thanks for the fix.

The MVC extensions product is soo powerful!!  saves me soo much time!

Thanks,

Josh
0
Rick
Top achievements
Rank 1
answered on 04 Jan 2011, 08:21 PM
I wasn't clear what the problem was that caused the issue from the tread (granted I didn't inspect the source), but I have encountered this as well and my symptoms might be different.

It seems if you define a CSS group, set combine to true, but never add a CSS file to the group, the asset handler won't set the MIME type to anything (according to the network sniffer in the IE 9 dev tools).

Does the hotfix address this issue as well?

Rick
Tags
General Discussions
Asked by
Joshua
Top achievements
Rank 2
Answers by
T. Tsonev
Telerik team
Joshua
Top achievements
Rank 2
Rick
Top achievements
Rank 1
Share this question
or