AEM list teaser images redirect on every request

A page can look correct while its list teaser images take an extra redirect on every view. An open AEM Core Components report describes a List v2/v3 teaser URL whose timestamp comes from the List node, while the image servlet expects the featured-image node's timestamp. That is a reported behavior in specific component versions, not a claim that every AEM site is affected.

Prove the request path

Capture the image URL from the rendered HTML and request it without following redirects. Record the first status, Location, cache headers, and the eventual image response. Compare a list item that returns 302 with one that returns 200. If only suffix-form .coreimg URLs from list teasers redirect, check the List, Teaser, featured image, and DAM asset modification times. Adobe's List component guide helps identify the component and version in use.

Separate a code defect from cache policy

A CDN rule cannot turn a consistently wrong image URL into a stable one. A redirect may also lack the caching headers applied to successful image responses, multiplying work at the edge. Confirm whether your deployed Core Components version and proxy models match the report before copying any workaround. A local model override needs a regression test for both image delivery and the data layer's modification date.

Define the release check

Test a List teaser after changing only the list, only the featured image, and only the asset. The rendered URL should return 200 directly in each case. Ask the delivery team for an HTTP trace and a version-specific fix or contained workaround, not a generic cache purge.

Adovo’s view

The cache cannot repair a URL the page keeps generating incorrectly. Fix the source of the image identity, then measure the edge behavior. A successful visual render is weaker evidence than one clean request.