[MAGNOLIA-3865] AddMimeMappingTask does not create extension node data Created: 20/Oct/11  Updated: 03/Dec/13  Resolved: 03/Dec/13

Status: Closed
Project: Magnolia
Component/s: updatemechanism
Affects Version/s: 4.4.5
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Matt Dertinger Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File AddMimeMappingTask.java.patch    
Template:
Patch included:
Yes
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:

 Description   

Hi,

Currently, AddMimeMappingTask.java does not create and set node data for extension in it's doExecute method.

Patch is attached.

Let me know if you have any questions.

Cheers,
Matt



 Comments   
Comment by Matt Dertinger [ 24/Oct/11 ]

Hi,

After doing some more testing, it looks like if the extension node data is not present, then the name of the content node is used. Therefore, the content is still served with the correct mime-type in the response header.

So, I'm not sure if the attached patch is needed or not.

Thoughts?

Cheers,
Matt

Comment by Tobias Mattsson [ 03/Dec/13 ]

Correct, if the extension is not explicitly set the node name is used.

Generated at Mon Feb 12 03:50:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.