For Domains More Than One We Need To Use CloudFlare 301 Redirect Match Like That on a Apache2 Server to Forward the URL to Another Domain. This is also needed to point naked domains towards the www subdomain. Among the DNS Service Providers discussed before, CloudFlare is a Free Option and widely known. This guide on CloudFlare 301 Redirect Match gives any level of users a clear how to do idea.
CloudFlare 301 Redirect Match : Basics You Need To Know
There are many domain records associated with a domain. In case of naked domain hosted on free Heroku Cloud or OpenShift, we basically need an IP address to point towards the server. This is the A Name or may be AAAA Name. They are, IPv4 and IPv6 addresses, respectively. If your domain is thecustomizewindows.com and you want to do CloudFlare 301 Redirect Match with the domain jima.in, you should have an IP address – if you use thecustomizewindows.com‘s server IP for jima.in, it actually becomes a redirection at DNS level. Other ways are pointed before. If you ever used any server to host the domain jima.in, using that IP actually works, regardless of the settings of the server. The reason is nothing – you are actually adding Page Rule, which from networking point of view is one level up.
CloudFlare 301 Redirect Match : Guide
Advertisement
---
Most commonly, we have very few range of need of redirection. Naked Domain to www redirect and vice versa is the most commonly done. Next is the 301 Redirect Match with the active website (thecustomizewindows.com) in our example with the domain added on CloudFlare (jima.in in our example). After creating the account and adding the domains, clearly there are two places to tweak within the CloudFlare control panel.
This infographics shows everything :
In typical case, if one domain is domain-to-be-redirected.tld and another is domain-towards which-will-be-redirected.tld, then the entry will be :
1 2 3 | Edit Pattern [http://domain-to-be-redirected.tld/*] Forwarding [https://domain-towards which-will-be-redirected.tld/$1] Forwarding type [301] |
In our case, one URL :
1 | http://jima.in/rssfeed.asp |
is redirected to
1 | https://thecustomizewindows.com/rssfeed.asp |
Now our server settings (or WordPress Plugin) will handle it :
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | curl -I https://thecustomizewindows.com/rssfeed.asp HTTP/1.1 301 Moved Permanently Server: nginx Date: Tue, 03 Mar 2015 07:57:18 GMT Content-Type: text/html; charset=utf-8 Connection: keep-alive Expires: Mon, 28 Dec 2015 07:57:18 GMT Cache-Control: max-age=25920000 X-Powered-By: HHVM/3.5.1 Set-Cookie: PHPSESSID=ebb5548868706c678042e7bfee5bfabf; path=/ Last-Modified: Wed, 16 Apr 2014 20:33:56 GMT Location: https://thecustomizewindows.com/rss/ X-Frame-Options: SAMEORIGIN X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Cache-Control: Public Alternate-Protocol: 443:npn-spdy/3 Strict-Transport-Security: max-age=31536000; includeSubDomains; preload |
This is the exact desired settings for the right SEO link juice. It avoids many issues with full HSTS websites.
