[MAGNOLIA-6588] MAGNOLIA-6478 Breaks content type for .resources (ClasspathSpool) Created: 09/Mar/16  Updated: 05/Sep/16  Resolved: 01/Apr/16

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.3.13
Fix Version/s: 5.3.15, 5.4.6

Type: Bug Priority: Major
Reporter: Ronald Ten Berge Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-6478 Don't set Content-Type header in Cont... 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 38
Story Points: 3

 Description   

Hi,

We are experiencing a problem with the loading of resources in Internet Explorer. After some investigation, we found out that the "Content-Type" header is missing from all the resources served by the ClasspathSpool.

I've traced the problem back to MAGNOLIA-6478 and pull request https://git.magnolia-cms.com/projects/PLATFORM/repos/main/pull-requests/70/diff. The mimeType for the response was previously being set before the call to chain.doFilter(). But this is now happening after chain.doFilter(). So the content-type is always being set to null.



 Comments   
Comment by Marc Johnen [ 30/May/16 ]

The solution is to exchange the ResponseContentTypeVoter with RequestExtensionVoter. The --release notes only say this class has become deprecated.

"ResponseContentTypeVoter has became deprecated and has been replaced by --RequestExtensionVoter to better reflect its function."

It seems an update of the voter is mandatory to keep a working system.-

This actually didn't solve the problem.

Generated at Mon Feb 12 04:15:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.