[MGNLUI-3742] Backport ExportAction from 5.4.x to 5.3.x Created: 07/Jan/16  Updated: 18/Jan/16  Resolved: 07/Jan/16

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

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

Issue Links:
dependency
is depended upon by MAGNOLIA-6479 Set correct MIME-type in JCR exports Closed
relation
is related to MGNLUI-3492 Add Action for yaml export in Configu... 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)
Sprint: Kromeriz 26
Story Points: 1

 Description   

The reason is that the old ExportAction is setting Content-Disposition incorrectly (which causes opening of JCR exports in browser window).

Even though this code is there:

        resource.getStream().setParameter("Content-Disposition", "attachment; filename=...");
        Page.getCurrent().open(resource, "", true);

The Content-Disposition header is set just to filename=... (without attachment;). (Probably a Vaadin issue - see https://vaadin.com/forum#!/thread/85013).

The JCR exports were disposed only because of (wrong) MIMEType application/octet-stream. After this was changed to application/xml, it behaves differently.


Generated at Mon Feb 12 09:09:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.