Page Comparison

...

• All AEM auto-generated renditions (filenames starting with cq5dam.* or cqdam.*) are ignored by default in the media resolving process (except cq5dam.video.* renditions). So, in most cases the original image is used to create virtual renditions. A new method getIncludeAssetAemRenditionsByDefault in MediaHandlerConfig gives your fine-grained control which auto-generated renditions are considered or not, and you can switch back to the previous behavior to set it to:

  Code Block
  language java
  @Override public @NotNull Set<AemRenditionType> getIncludeAssetAemRenditionsByDefault() { return Set.of(AemRenditionType.WEB_RENDITION, AemRenditionType.VIDEO_RENDITION, AemRenditionType.OTHER_RENDITION); }

• The default image quality for JPEG images is lowered from 98% to 85%. As before, you can overwrite this value in your MediaHandlerConfig. There is new method getDefaultImageQualityPercentage in MediaHandlerConfig which allows you to directly overwrite this value:

  Code Block
  language java
  @Override public double getDefaultImageQualityPercentage() { return 0.98d; }

• The support for the AEM Web-Optimized Image Delivery is enabled by default and is active only on AEMaaCS cloud images. That means wherever possible renditions are generated on the Adobe Edge by the Web-Optimized Image Delivery and not within the Java process. To disable this you can provide this OSGi configuration:

  Code Block
  language json
  "io.wcm.handler.mediasource.dam.impl.weboptimized.WebOptimizedImageDeliveryServiceImpl": { "enabled": false }

  • Web-Optimized Image Delivery cannot access custom renditions maybe created for assets (e.g. manual crops). If your project relies on additionally created asset renditions, you have to switch off the Web-Optimized Image Delivery and use the JVM-based rendition rendering to take them into account.

• SVG Files are served with a Content-Security-Policy header by default. This prevents XSS attacks as SVG files uploaded by authors may contain malicious JavaScript. This is blocked by default (“sandbox” mode). In special use cases this may break existing behavior, e.g. if you use JavaScript to animate loaded SVG images. In this case you can disabled the XSS protection (do this only if you are sure authors do not upload malicious SVG files):

  Code Block
  language json
  "io.wcm.handler.media.impl.MediaFileServlet": { "svgContentSecurityPolicy": false }

Related articles