[MAGNOLIA-5675] ExportCommand should set proper mimeType for xml files Created: 13/Feb/14  Updated: 04/Mar/19

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Daniel Lipp Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLCTS-51 Add UI Integration Test for Entire Do... Open
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)

 Description   

Since MAGNOLIA-5672 the following code would be executed with autosave:

    @Test
    public void testAutosaveOnDownload() {
        driver.navigate().to("http://spatialkeydocs.s3.amazonaws.com/FL_insurance_sample.csv.zip");
    }

The same thing did not work e.g for exporting an asset. As it turned out this is because MAGNOLIA-5672 enables autosave for certain mime types - e.g. "application/xml".

As our ExportCommand sets mimeType "application/octet-stream" for xml files this didn't do the trick



 Comments   
Comment by Daniel Lipp [ 13/Feb/14 ]

Ranked major because it blocks us from automating tests where we download files. Once it's resolved we can rate it down.

Comment by Daniel Lipp [ 13/Feb/14 ]

Looks like the ExportCommand could actually use info.magnolia.cms.beans.config.MIMEMapping to resolve mime types from file extensions (DRY).

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