Redirects with Custom CDN

hi @new_noob ,

Instead of rewrite rule,

You may cross check if server name and alias is correctly mentioned, if not try like below

e.g. 

ServerAlias ${CH_HUB_VHOST}

<VirtualHost *:80>
ServerName publish
ServerAlias mycdn.domain.com
# other configuration settings
</VirtualHost>

Thanks

Hi @new_noob ,

No, you do not need to manually update every single redirect rule.
You can centralize the fix using one of these 2 reliable methods depending on your setup.

Why This Happens

Apache’s RewriteRule creates redirects using:

  - A relative path (/index) => Apache prepends the current host (e.g., publish-xxx).

  - A fully qualified URL (https://%{HTTP_HOST}/index) => You control the domain in Location.

When you're behind CDNs like Akamai => Fastly => Adobe AEM, they pass their internal host to Apache. So unless you explicitly set the host using %{HTTP_HOST}, you get a Location header pointing to the origin, not your CDN domain.

Try below option:

Option 1: Add a Global Redirect Wrapper (Preferred for Many Rules)

If you already have lots of redirect rules like:

You don’t have to touch each one.

Instead, wrap your redirect logic in a global RewriteCond + RewriteRule` that prepends the host, like this:

What this does:

  - Prevents infinite loops with REDIRECT_STATUS

  - Converts any relative redirect into an absolute one using %{HTTP_HOST} (e.g., your Akamai CDN domain)

  - Keeps all your existing redirect rules unchanged

Option 2: Use mod_headers to Rewrite Location Header

If you want to be even cleaner and rewrite the Location header on all 301/302 responses, you can use:

Note:

  - This requires mod_headers

  - Works best when you're returning absolute URLs in redirects

  - %{HTTP_HOST}e uses the value from the environment variable

  - This is especially powerful if you can't control all rules but want a centralized fix.

Regards,
Amit