[MGNLRES-265] Correct content type for bypassed processed CSS files Created: 08/Mar/16  Updated: 29/Mar/22  Resolved: 12/Apr/16

Status: Closed
Project: Magnolia Resources Module
Component/s: resourceLoaders
Affects Version/s: 2.3.6
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Lea Hänsenberger Assignee: Antonín Juran
Resolution: Duplicate Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLRES-149 Concept for supporting processing res... Closed
duplicate
duplicates MGNLRES-254 Renderer needs to respect content typ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Kromeriz 39
Story Points: 3
Team: Nucleus

 Description   

When I set a CSS resource with template Processed CSS to be bypassed while developing Chrome refuses to load the stylesheet as stylesheet with the following error:

Resource interpreted as Stylesheet but transferred with MIME type text/html
Javascript files that are set to bypass also have Content-Type text/thml, but there the browsers do not complain.

I'm using Chrome Version 48.0.2564.116 (64-bit)

Please make sure that the resources have the correct Content Type in the response headers.



 Comments   
Comment by Antonín Juran [ 12/Apr/16 ]

Already fixed by MGNLRES-254 and MAGNOLIA-6452.

Generated at Mon Feb 12 06:49:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.