I had test it on Chrome and Firefox, but the bug only happens on Chrome. I had no error on browser console or error.log. I already saw the another thread about SVG, but the errors is not similar with the my. I saw in some sites people have similar problems on another CMS or Applications Services they solve their erros just editing the .htaccess puting this rule "AddType image/svg+xml svg svgz
AddEncoding gzip svgz", but on AEM we haven't .htaccess, so it not work for us.
But the plan HTML with <img src="mysvg.svg"> used on my component work well even on Chrome. It stop work when I put the html on AEM component and I refer the image from AEM Assets folder.
So if you select another file type - it works?
This requires some debugging this could be some issue with the 3rd party lib for SVG rendition AEM uses.
Please create a Support ticket for this.
Try Workaround:- AEM can be configured with ImageMagick Best Practices for Configuring ImageMagick
I have the same problem.
We’ve created a page in Adobe AEM using DAM to serve image files. PNG image files are being served OK, but SVG image files are not being displayed correctly in Chrome (Firefox actually displays it).
The problem is: AEM http response should be returning “Content-Type:image/svg+xml” but it is actually returning “Content-Disposition: attachment; filename="yt.svg"”.
If I try to open the URL directly, Chrome doesn’t display the image (instead, it tries to download it), while Firefox displays it.
If I access other websites that uses SVG, it works OK, because their server is returning the correct HTTP response. Only content served by DAM is not OK.
Is there any solution to this annoying problem?
By the way, I am using Adobe AEM 6.4.
Same problem here.
I've tried to set the file under Apache Sling Content Disposition Filter to avoid it, but it seems no working as expected.
Even though it is not a suitable solution if is needed to set every image in that bundle configuration.
Does anyone find a solution?
3 people found this helpful
Adobe advised to use the org.apache.sling.security-1.1.12.jar to fix this rendering issue. It worked for us. Thank you.
Thank you! It render fine now
This fix helps. But this works only for administrative users. This is still broken when logging in as Author. What is the permanent fix?
In AEM 6.4 I've check with different users in different environments:
Author admin: svg renders
Author with an author account: svg renders
Publish with anonymous account: svg renders