-
Improvement
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Kromeriz 26
-
1
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.
Acceptance criteria
- is depended upon by
-
MAGNOLIA-6479 Set correct MIME-type in JCR exports
- Closed
- is related to
-
MGNLUI-3492 Add Action for yaml export in Configuration App.
- Closed