[MGNLRES-207] Uploaded ftl are detected as application/octet-stream Created: 31/Aug/15  Updated: 29/Mar/22  Resolved: 04/Sep/15

Status: Closed
Project: Magnolia Resources Module
Component/s: None
Affects Version/s: 2.4.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.5d
Original Estimate: Not Specified

Issue Links:
supersession
is superseded by MGNLRES-187 Add upload action for new resource files 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
Epic Link: Phase out in-place templating app
Sprint: Sprint (Basel) 8
Story Points: 3
Team: Nucleus

 Description   

Uploaded ftl are detected as application/octet-stream and thus are not editable:

  • depends on mime type not defined under /server/MIMEMapping?


 Comments   
Comment by Federico Grilli [ 01/Sep/15 ]

For some reason (application server configuration?) some mime types which we need to handle (such as ftl) end up as application/octet-stream in the request ContentType header (see com.vaadin.server.communication.FileUploadHandler.doHandleSimpleMultipartFileUpload(..)) which makes it impossible to e.g. edit them. In such case replaces application/octet-stream with a generic custom text type, e.g. text/x-<file-extension>

Comment by Federico Grilli [ 04/Sep/15 ]

The fix has been made directly under MGNLRES-187

Generated at Mon Feb 12 06:48:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.