Handle thousands of redirects | Community
Skip to main content
D
DanielJi6
Level 1
February 9, 2026
Question

Handle thousands of redirects

  • February 9, 2026
  • 2 replies
  • 11 views

Hi All.

Is there a risk in having more than 5k+ redirects managed by the Dispatcher? Is there any recommendation from Adobe to manage this specific scenario?

Thanks.

2 replies

Vishal_Anand
Vishal_Anand
Level 4
February 9, 2026

​@DanielJi6  Yes - managing 5k+ redirects in the Dispatcher can cause performance, maintainability and operational risks. Adobe and web‑server best practices recommend offloading or using lookup‑style maps rather than many regex rules.

 

Risks

  • Performance: large rule sets slow request processing (CPU/latency) and increase memory use.
  • Reload cost: updating rules may require service reloads causing brief impact.
  • Complexity: hard to maintain, higher chance of mistakes and missed redirects.
  • Cache inefficiency: dispatcher cache hits/misses can be affected if redirects are not handled at edge.

Practical recommendations -

  • Edge/CDN redirects (preferred): implement redirects at CDN (CloudFront, Akamai, Fastly) — lowest latency and offloads origin.
  • Web‑server lookup maps: use webserver RewriteMap (Apache) or equivalent (IIS rewrite provider) — single fast lookup file instead of many rules.
  • Dispatcher config with lookup: if you must keep it on origin, serve a single lookup (map) and avoid thousands of regex entries.
  • Avoid per‑request complex regex: don’t use many RedirectMatch/mod_rewrite rules — they’re slow at scale.
  • AEM alternatives: Sling ResourceResolver mappings or a small lookup servlet can work but typically are less performant than CDN or webserver maps.

Quick checklist before implementation:

  • Can redirects be moved to CDN? (best fix)
  • Can you convert rules into a single lookup map?
  • Performance test with realistic traffic and measure latency/CPU.
  • Plan incremental rollout and monitoring/alerts.
D
DanielJi6Author
Level 1
February 9, 2026

Thanks.

 

Is there an example for lookup maps for AEMaaCS?


Can this configuration be done in Fastly for AEMaaCS?

Vishal_Anand
Vishal_Anand
Level 4
February 9, 2026

​@DanielJi6 Yes — use Fastly Edge Dictionaries + a small VCL snippet to implement thousands of redirects at the CDN edge. That’s the recommended approach for AEMaaCS (fast, low‑latency, offloads origin).

 

You’ll likely need to coordinate with Adobe Cloud/DevOps because AEMaaCS Fastly config is centrally managed; if you don’t have direct Fastly access, raise a Cloud Manager/Support request.

 

What you’ll build

  • An Edge Dictionary that stores old-path -> new-URL key/value pairs (one row per redirect).
  • A Request-phase VCL snippet that looks up req.url.path in the dictionary and issues a 301/302 when a match is found.
  • Optionally: prefix/wildcard handling, fallback logic, and caching/monitoring.
Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity Advisor
Community Advisor
February 9, 2026

​@DanielJi6 yes dispatcher may not be best bet for large scale redirects.

 

Best place to add redirects are

1. CDN - in cloud its Fastly or if you have your own CDN.

2. Add a reverse proxy like Nginx which is very performant in handling redirects.

Terms & ConditionsAccessibility statement

Loading footer...