[MGNLACTIVATION-131] Activation sets incorrect content type Created: 23/Jun/16  Updated: 13/Jul/16  Resolved: 13/Jul/16

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.6, 5.4.4

Type: Bug Priority: Neutral
Reporter: Antonín Juran Assignee: Evzen Fochr
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3h
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-6675 ContentTypeFilter should warn if cont... Closed
dependency
is depended upon by MGNLXAA-98 'No content type set' exception while... 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 52
Story Points: 5

 Description   

ResponseCode - 204 No Content was set in RecieveFilter.



 Comments   
Comment by Roman Kovařík [ 07/Jul/16 ]

Reopened: we set the application/gzip on the other side (receive filter) where we're actually getting the zip file. We should set another status code than 200 (maybe 204 - no content type) or different content type.

Comment by Jan Haderka [ 07/Jul/16 ]

application/zip if what we send is single zip file. If however we send multiple files, encoded as multipart then the type should be set to multipart/form-data.

Generated at Sun Feb 11 22:59:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.