Adobe Core Components not serving images from the dam

[AEMWizard]

Hi guys, can someone please explain when using Adobe Core Component's why are all images being served, not from /content/dam/my-site?

For example, this is the WKND project that I have installed on my local machine with the dispatcher turned on, and what I can see here is the images are being served via _jcr_content. And so, in order for me to serve these images, I must enable PT from the dispatcher level.

RewriteRule ^/(*_jcr_content.*) $1 [PT] 

<img src="/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.png/1660323783259/article-01-picture-01.png" srcset="/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.100.png/1660323783259/article-01-picture-01.png 100w,/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.200.png/1660323783259/article-01-picture-01.png 200w,/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.300.png/1660323783259/article-01-picture-01.png 300w,/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.400.png/1660323783259/article-01-picture-01.png 400w,/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.500.png/1660323783259/article-01-picture-01.png 500w,/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.600.png/1660323783259/article-01-picture-01.png 600w,/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.700.png/1660323783259/article-01-picture-01.png 700w,/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.800.png/1660323783259/article-01-picture-01.png 800w,/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.900.png/1660323783259/article-01-picture-01.png 900w,/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.1000.png/1660323783259/article-01-picture-01.png 1000w,/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.1100.png/1660323783259/article-01-picture-01.png 1100w,/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.1200.png/1660323783259/article-01-picture-01.png 1200w,/us/en/magazine/guide-la-skateparks/_jcr_content/root/container/container/contentfragment/par2/image_copy.coreimg.60.1600.png/1660323783259/article-01-picture-01.png 1600w" loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="765" height="535" alt="Ultimate Guide to LA Skateparks">

[lukasz-m · Accepted solution]

Hi @AEMWizard,

This is because Core Components are using Adaptive Image Servlet to automatically select the most appropriate rendition to display based on the size of the container in which it is displayed.

Please explore below documentation for all the details:

• https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/adaptive...
• https://github.com/adobe/aem-core-wcm-components/wiki/The-Adaptive-Image-Servlet

Last but not least, documentation that describes URL structure:

• https://github.com/adobe/aem-core-wcm-components/wiki/The-Adaptive-Image-Servlet#url-formats