A forwarded website can be accomplished by first creating a subdomain or addon domain in the control panel, then using an .htaccess in document root to redirect all traffic to the new web site using mod_rewrite.
- Forwarded domain: domain that will redirect to the target domain
- Target domain: domain that is the final destination of the forwarded domain
- Path capture: take the path in the url, e.g.
http://example.com/foo/bar/baz, and transfer that path to the target domain. This is accomplished with a regex capture
Direct Forward, No Path Capture
Add the following lines to your .htaccess file in the document root of the forwarded domain (or subdomain) that you would like to redirect. Once a user accesses the website, the browser location will change to reflect the target domain.
RewriteRule ^ http://DESTINATIONSITE/OPTIONALURL [R=301,L]
Direct Forward, Path Capture
RewriteRule ^(.*)$ http://DESTINATIONSITE/$1 [R=301, L]
Proxied Forward, Path Capture
A proxied forward will attempt to keep the original domain in the Location bar of the browser and impersonate the target site as if it were hosted under the forwarded domain. There are several limitations to this approach that are only resolvable by manipulating the stream as it comes over the wire, which is also beyond the scope of this article but accomplished with reverse proxy middleware as is used in apnscp to redirect cp.apnscp.com to each platform’s control panel.
RewriteRule ^(.*)$ http://DESTINATIONSITE/$1 [P,L,QSA]
A proxied forward will leak the target domain’s location if the target domain uses absolute URLs or sends a “Location:” header as if forwarding in one of the two above examples.
Each redirect in the aforementioned examples uses “301”. There are 4 types of redirects to familiarize yourself with, each code is pragmatic in that it instructs the browser or search engine how to handle the response:
- 301: Permanent redirect. Clients making subsequent requests for this resource should use the new URL. Clients should not follow the redirect automatically for POST/PUT/DELETE requests.
- 302: Redirect for undefined reason. Clients making subsequent requests for this resource should not use the new URL. Clients should not follow the redirect automatically for POST/PUT/DELETE requests.
- 303: Redirect for undefined reason. Typically, ‘Operation has completed, continue elsewhere.’ Clients making subsequent requests for this resource should not use the new URL. Clients should follow the redirect for POST/PUT/DELETE requests.
- 307: Temporary redirect. Resource may return to this location at a later point. Clients making subsequent requests for this resource should use the old URL. Clients should not follow the redirect automatically for POST/PUT/DELETE requests.
Credit: Bob Aman, StackOverflow
- URL Rewriting Guide (apache.org)
- Regular Expression Tutorial – Learn How to Use Regular Expressions (regular-expressions.info)
- Redirection – Best Practices (moz.com)