301 Redirect not working on Cloud

Hi @love_sharma,

Try to add a host and a protocol to your rule:

RewriteRule ^/xyz\/?(.*)$ ${PROTOCOL}://%{HTTP_HOST}/abc [R=301,L]

In addition, consider implementation of https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/pipeline-free-url-redirects on your project.

Best regards,

Kostiantyn Diachenko.

Hi @love_sharma ,

I believe the following rewrite rule should be enough:

RewriteEngine On
RewriteRule ^/xyz/?$ /abc [R=301,L]

This rule will work across all domains and redirect /xyz to /abc with a 301 status. It’s sufficient for this type of redirection and doesn't require relying on Sling Mappings.

Thanks.

Thanks.

Hi @love_sharma ,

301 redirect from /xyz to /abc on AEM as a Cloud Service, ensuring it respects the domain (qa.myproject.com or otherwise) and avoids redirecting to the internal publish-domain, follow these specific steps:

1. Use Apache Rewrite Rule with Correct Host Preservation

In your Apache configuration (typically in your vhost or dispatcher rules):

This will:

  - Match /xyz or /xyz/

  - Redirect to the same host (e.g., qa.myproject.com)

  - Use https explicitly (important for Cloud)

  - Ensure the redirect is a 301 (permanent)

2. Optional – Force Protocol to HTTPS (Recommended)

If your domain might be hit over HTTP and you want to force HTTPS:

Place this above your /xyz rule if needed.

3. Do NOT use Sling Mapping for Simple Redirects

You do not need Sling mappings (/conf/global/mappings) for simple path-to-path redirects. These are mostly used for vanity URLs and internal resource resolution.

Final Dispatcher Snippet (Minimal Example)

If you're using AEM Cloud Dispatcher SDK, add this inside your custom rewrite.rules in conf.d/rewrites.

Regards,
Amit

AEM documentation and troubleshooting refer specifically to correct handling of virtual hosts and hostname/redirect processing:

• For multi-domain setups, you must ensure that your RewriteRule or redirection keeps the original hostname Using the Dispatcher with Multiple Domains
• Cloud 5 - Fix Your... Rewrites discusses how rewrites and redirects should be carefully crafted to not “leak” internal publish hostnames

Solution

Use a relative URL in your redirect

This is what you're attempting, and should work:

RewriteRule ^/xyz/?$ /abc [R=301,L]

or

RewriteRule ^/xyz(/.*)?$ /abc [R=301,L]

• By specifying a relative URL (/abc), the client’s browser should stay on the same domain, using the Host header of the original request.

Check for RewriteBase and VirtualHost config

• Make sure you are running this rule inside the correct <VirtualHost> block for qa.myproject.com.
• If you are, and still getting a redirect to https://publish-domain/abc, there may be another RewriteRule firing first, or your dispatcher farm/vhost (or AEM itself) is configured to externalize/resolve using the publisher’s DNS name.
• Try enabling RewriteLog to trace what rule is being executed.

Avoid hardcoded domains

• Never use absolute URLs with internal domains in the rewrite/redirect rules.
• Always use relative paths only unless you want to specifically redirect to another domain.

Check /externalizer config in AEM

• If you use AEM's Externalizer service in custom code or config, ensure the publish environment is registered with the correct external/public base URL, not the internal publish hostname.

Sling Mappings

• Sling mappings are not usually involved for this particular redirect. If you do have custom mappings, make sure none are producing absolute URLs with internal hostnames for /abc.

TL;DR

• Keep your redirect rule as:
  RewriteRule ^/xyz/?$ /abc [R=301,L]
• Check that this is inside the VirtualHost config for your public domain.
• Make sure there’s no earlier rule or AEM config causing an absolute URL with the internal publish host.
• You do NOT need a full absolute URL for the redirect target, unless you are explicitly redirecting across domains.

References:

• Using the Dispatcher with Multiple Domains
• Cloud 5 - Fix Your... Rewrites

@love_sharma 

Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!