Why do I still still Resizer v1 requests, after migrating to Resizer v2?

Last updatedView as Markdown

Question

Why do I still still Resizer v1 requests, after migrating to Resizer v2?

Answer

After migrating to Resizer v2, it’s normal to still see some Resizer v1 requests. This can happen for several reasons: 

  • Search engines may have indexed v1 image URLs, which take time to update.

  • The migration process may have missed some v1 image URLs.

  • V1 images have a one-year cache (TTL). Arc XP is not clearing this cache as part of v1 deprecation, so those URLs can continue serving from cache for up to a year. After that, they’ll redirect to Resizer v2.

Additionally, some URL types are exempt from v1 deprecation and will continue using v1 until Arc upgrades them:

  • Arc XP Native Specification (ANS) URLs (paths including arc-anglerfish- or arc-photo-)

  • Video thumbnail URLs (paths including arc-goldfish--thumbnails*)

  • URLs used by Queryly

More information