Edge Delivery Encoded URLs | Community
Skip to main content
C
CurtisDe2
August 22, 2025
Solved

Edge Delivery Encoded URLs

  • August 22, 2025
  • 1 reply
  • 532 views

I am currently trying to create redirects for a site that is being managed with Edge Delivery. When the source URL contains encoded entities (such as %20) or any special characters beside '-', I get a 404 error. When saving the spreadsheet with these redirects, the sheet saves fine and I see the JSON object with the valid and invalid redirects.

 

For example:

This works.

 

Destination: /my-page

Source: /my-old-page

 

----

These do not work.


Destination: /my%20page

Source: /my-old-page

 

Destination: /my+page

Source: /my-old-page

 

Is this a known limitation of Edge Delivery? Are there any workarounds or does Edge Delivery require every URL to be in a slug style?

Best answer by VishalKa5

Hi @curtisde2 ,

 

1. Edge Delivery supports only slug-style URLs

Allowed: lowercase letters (a–z), numbers (0–9), and dashes (-).

Not allowed: spaces (%20), plus signs (+), or other special characters.

If such characters are used, Edge Delivery returns 404.

2. Why it happens

Edge Delivery automatically cleans and normalizes URLs.

It enforces simple, SEO-friendly slugs to avoid broken links or inconsistencies.

3. Workarounds

Best practice: Rename pages and redirects to use clean slug URLs.

If special characters must be supported:

Add redirect rules at the CDN level (Akamai, Fastly, Adobe-managed CDN).

Or use AEM dispatcher rewrite maps (pipeline-free redirects) for more flexibility.

 

Yes, this is a known limitation. Edge Delivery requires slug-style URLs, and anything with encoded or special characters must be handled outside of Edge Delivery.

 

Thanks & regards,

Vishal

1 reply

VishalKa5
VishalKa5Accepted solution
Level 5
August 22, 2025

Hi @curtisde2 ,

 

1. Edge Delivery supports only slug-style URLs

Allowed: lowercase letters (a–z), numbers (0–9), and dashes (-).

Not allowed: spaces (%20), plus signs (+), or other special characters.

If such characters are used, Edge Delivery returns 404.

2. Why it happens

Edge Delivery automatically cleans and normalizes URLs.

It enforces simple, SEO-friendly slugs to avoid broken links or inconsistencies.

3. Workarounds

Best practice: Rename pages and redirects to use clean slug URLs.

If special characters must be supported:

Add redirect rules at the CDN level (Akamai, Fastly, Adobe-managed CDN).

Or use AEM dispatcher rewrite maps (pipeline-free redirects) for more flexibility.

 

Yes, this is a known limitation. Edge Delivery requires slug-style URLs, and anything with encoded or special characters must be handled outside of Edge Delivery.

 

Thanks & regards,

Vishal

    Terms & ConditionsAccessibility statement

    Loading footer...