[MSITEMESH-38] No need to override MagnoliaSiteMeshFilter#bufferAndPostProcess since MAGNOLIA-6478 Created: 13/Jan/16  Updated: 01/Feb/16  Resolved: 13/Jan/16

Status: Closed
Project: SiteMesh
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.2

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.5h
Original Estimate: Not Specified

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
Epic Link: Move setting of Content-Type header to where the content is generated
Sprint: Kromeriz 28
Story Points: 1

 Description   

This is not true anymore:

Magnolia specific implementation of ContentTypeFilter#bufferAndPostProcess(). We need to call: <code>responseBuffer.setContentType(responseBuffer.getContentType());</co
-     * in comparison with original method since
-     * - {@link info.magnolia.cms.filters.ContentTypeFilter} which sets content type runs before {@link org.sitemesh.webapp.SiteMeshFilter}.

Moreover sitemesh fails since MAGNOLIA-6478 when trying to set null content type.



 Comments   
Comment by Roman Kovařík [ 13/Jan/16 ]

Review, QA to be done after release of 5.4.4.

Generated at Mon Feb 12 10:57:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.