Home / server / Questions / 971829
Accepted
Jesse יִשַׁי
Asked: 2019-06-18 21:01:45 +0800 CST

Apache rewrite: sub.DOM1.TLD1/path > sub.DOM2.TLD2/path

  • 772

...the MAYBE-dup answer does solve my problem, but the question doesn't.

Do TWO things:

  1. Keep subdomain before

  2. Keep path after

I can't find ONE .htaccess or Apache config that does BOTH anywhere on SE or elsewhere on the web:

Via Apache .htaccess rewrite, forward the old domain, but keep BOTH the same subdomain AND path/after.

From:

samesubdomain.domain1.tld1/same/path

To:

samesubdomain.domain2.tld2/same/path

I have many subdomains AND trailing addresses. I am migrating an old site, but need my old subs and their pages to still work on the new domain.

Not-but-close duplicates: (The answers address my problem, but the question itself does not describe my problem, but this solved my problem also.)

Redirect wildcard subdomain to same subdomain on different domain

Courtesy the MAYBE-dup answer, for the subdomain, I currently have:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(.+\.)?domain1.com$ [NC]
RewriteRule ^ http://%1domain2.com%{REQUEST_URI} [R=301,L]

...now, I need to add the/path half WITHOUT conflicting with this code.

.htaccess

1 Answers

  1. Best Answer

    Although the linked question doesn't specifically state this, the code does actually copy the URL-path (and any query string) as well. Although the answers are admittedly lacking in any explanation.

    Assumptions:

    • There is always a subdomain. So, you don't want to redirect the domain apex. ie. domain1.tld1 (with no subdomain) does not redirect to domain2.tld2.

    Near the top of your root .htaccess file:

    RewriteEngine On

RewriteCond %{HTTP_HOST} ^([^.]+)\.domain1\.tld1 [NC]
RewriteRule (.*) https://%1.domain2.tld2/$1 [R=302,L]

    The RewriteCond directive captures the subdomain from the request. The %1 backreference in the RewriteRule substitution is a backreference to the captured subdomain (ie. ([^.]+)).

    The $1 backreference contains the URL-path, captured by the RewriteRule pattern, ie. (.*).

    Note that I specifically omitted the trailing $ (end-of-string anchor) on the CondPattern in order to match FQDN, that end in a dot.

    Any query string is passed through unchanged.

    Note that this is currently a 302 (temporary) redirect. Always test with 302s to avoid caching issues. If you've previously tested with 301s then you will need to make sure you've cleared your browser cache.

    RewriteEngine On
RewriteCond %{HTTP_HOST} ^(.+\.)?domain1.com$ [NC]
RewriteRule ^ http://%1domain2.com%{REQUEST_URI} [R=301,L]

    ...now, I need to add the/path half WITHOUT conflicting with this code.

    The code already contains the URL-path part. That's what the %{REQUEST_URI} part is in the RewriteRule substitution string. The REQUEST_URI server variable contains the full URL-path. This is just another way of doing the same thing as I did above - I used a backreference $1 instead. (Note that the REQUEST_URI server variable contains the slash prefix, whereas the backreference I used does not, hence the difference in slashes in the substitution string.)

    This code is missing a backslash escape on the literal dot in .com.

    Note that this solution makes the subdomain optional. It will redirect domain1.com (no subdomain) to domain2.com.

    • 1