[MGNLDMS-130] MIME type not set correctly? Browser are not able to display images from the dmg when linking directly to them. Created: 14/Jul/08  Updated: 10/Sep/08  Resolved: 10/Sep/08

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: 1.2.4
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Will Scheidegger Assignee: Magnolia International
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When trying to load & display an image file stored in the dms in the browser (i.e. directly via the URL like .../dms/path/to/file.png instead of via an <img /> tag) webbrowsers will download the image instead of displaying it. Also dragging a displayed image from a magnolia webpage (i.e. <img src="${pageContext.request.contextPath}/dms/path/to/file.png}" />) to an image app like Photoshop will result in an error message. This makes me believe that the Content-type headers for the documents in the DMS are not set correctly.



 Comments   
Comment by Magnolia International [ 10/Sep/08 ]

The Content-Type header is set properly (well, according to the document node, that is)

The download/inline issue is because we set the Content-Disposition header to "attachment". See MGNLDMS-100 for potential fixes.

As for your drag'n'drop issue, I haven't been able to reproduce it, at least with 1.2.6-SNAPSHOT - could you elaborate on how this is behaving differently than with other sites, what the error is, etc.. ?

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