[MAGNOLIA-6478] Don't set Content-Type header in ContentTypeFilter Created: 31/Dec/15  Updated: 31/Aug/16  Resolved: 08/Jan/16

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

Type: Improvement Priority: Neutral
Reporter: Robert Šiška Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1h 40m
Original Estimate: Not Specified

Issue Links:
causality
is causing MAGNOLIA-6588 MAGNOLIA-6478 Breaks content type for... Closed
is causing MGNLMODSTR-6 ModifystreamFilter never wraps respon... Closed
dependency
is depended upon by MAGNOLIA-6452 Add contentType field to renderers 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)
Release notes required:
Yes
Date of First Response:
Epic Link: Move setting of Content-Type header to where the content is generated
Sprint: Kromeriz 28
Story Points: 3

 Description   

See epic for explanation.



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

Reopened: reverted from master cause the migration of content type voters should go with this ticket

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