Custom Domain Redirection, In Addition To A Referral Servers
Tuesday, August 28, 2018
Edit
One of the advantages of custom domain publishing, too the domain root to published URL redirection, used to hold upwardly transparent redirection of the URLs.
As Blogger weblog owners operate past times away to a greater extent than sophisticated amongst their blogs, too custom dwelling identify pages (aka "landing pages"), operate past times away to a greater extent than popular, nosotros bring weblog owners amongst concerns nearly dwelling identify page access too domain root redirection. We are likewise seeing concern amongst straight access to specific posts - amongst posts advertised, using the domain root URL.
In roughly cases, redirection exclusively shows the reader the weblog dwelling identify page, equally the get-go thought of the weblog - fifty-fifty amongst a specific postal service beingness linked inwards the advertised URL.
For my custom domain "nitecruzr.net", "blogging.nitecruzr.net" is the target of the domain root redirect.
This postal service "Custom Domain Redirection, And "A" Referral Servers" has a URL of " ". This postal service "Custom Domain Redirection, And "A" Referral Servers", should bring an alternate URL of "https://makeaseoquick.blogspot.com//search?q=".
Click on the iv links, inwards the paragraph at 1 time above, too compare the results - if you lot don't all the same encounter the seriousness here. Please. It's non a cosmetic detail.
This postal service "Custom Domain Redirection, And "A" Referral Servers", when linked equally "https://makeaseoquick.blogspot.com//search?q=", instead redirects to "http://nitecruzr.net/".
This postal service "Custom Domain Redirection, And "A" Referral Servers", when linked equally "https://makeaseoquick.blogspot.com//search?q=", instead redirects to "https://nitecruzr.net/".
Note that this weblog does non all the same purpose "HTTPS Redirect", then if you lot click on a link to "Custom Domain Redirection, And "A" Referral Servers" you lot volition encounter " ".
Here's a diagnosed illustration of the problem.
Here's a an illustration of this employment - diagnosed using a previous postal service blogging.nitecruzr.net/2016/08/delete-permanently-means-delete.html
A normal redirect - to "blogging.nitecruzr.net/2016/08/delete-permanently-means-delete.html"
A normal redirect - to the specific post, using HTTPS.
A broken redirect - to "blogging.nitecruzr.net"
A broken redirect - to the weblog dwelling identify page, using HTTPS.
Unfortunately, roughly weblog owners are observing that redirection of a specific root URL - perhaps a custom landing page, or a specific postal service advertised using the root URL - appears to atomic number 82 exclusively to the dwelling identify page of the published blog.
This is a employment amongst domain / website design, inwards general - too amongst Blogger custom domain design, inwards particular.
The domain root to published URL (for most blogs, the "www" host) appears to purpose a version of frame forwarding, amongst roughly blogs beingness reported.
I never recommend using Frame Forwarding, inwards the custom domain DNS setup.
One of the disadvantages of frame forwarding is that redirects using frame forwarding driblet the postal service URL.
We've been seeing this employment reported, for several years.
The problem, rarely - simply non never - reported, started several years ago. This was earlier HTTPS for BlogSpot - too fifty-fifty further earlier HTTPS for custom domains - was rolled out.
This was before long afterwards nosotros started observing other problems involved, inwards the deployment of HTTPS.
The get-go HTTPS number was reported inwards 2014. HTTPS for BlogSpot was rolled out inwards 2015.
I'm betting nosotros get-go saw reports of the postal service URL beingness lost, inwards the ""http://xxxxxxx.whatever.com/whatever.html" -> ... -> "https://www.whatever.com"" was perhaps ii years ago. During deployment of HTTPS.
My approximate is that Blogger Engineers upgraded the domain root servers ("A" address) redirection code, to back upwardly HTTPS - too made a occupation concern conclusion to purpose frame forwarding.
From what I've seen of Blogger Engineering inwards full general - too custom domain pattern inwards exceptional - I am convinced that if they decided that frame forwarding is necessary, it's necessary. Until they tin right the problem, that is. My advice to every domain possessor to not purpose registrar supplied frame forwarding inwards the domain DNS, notwithstanding.
I tin exclusively promise that nosotros volition encounter this employment corrected, this decade. Remain optimistic - too written report the problem, when it tin hold upwardly identified.
It appears that roughly of the #Blogger custom domain "A" address cry servers are using "Frame Forwarding", instead of "Referral", to redirect the domain root to the published URL. Frame forwarding strips away the postal service address part of the URL - leaving exclusively the domain root.
Some weblog owners purpose the domain root to advertise their weblog posts - too are seeing exclusively the weblog dwelling identify page, instead of the private posts, when linking to the posts.
https://productforums.google.com/d/topic/blogger/NtQHoVNJ5PM/discussion
https://productforums.google.com/d/topic/blogger/pePwPhr_H-Y/discussion
https://productforums.google.com/forum/#!category-topic/blogger/pePwPhr_H-Y
https://productforums.google.com/forum/#!category-topic/blogger/nr-cIIgjBGg
As Blogger weblog owners operate past times away to a greater extent than sophisticated amongst their blogs, too custom dwelling identify pages (aka "landing pages"), operate past times away to a greater extent than popular, nosotros bring weblog owners amongst concerns nearly dwelling identify page access too domain root redirection. We are likewise seeing concern amongst straight access to specific posts - amongst posts advertised, using the domain root URL.
In roughly cases, redirection exclusively shows the reader the weblog dwelling identify page, equally the get-go thought of the weblog - fifty-fifty amongst a specific postal service beingness linked inwards the advertised URL.
For my custom domain "nitecruzr.net", "blogging.nitecruzr.net" is the target of the domain root redirect.
This postal service "Custom Domain Redirection, And "A" Referral Servers" has a URL of " ". This postal service "Custom Domain Redirection, And "A" Referral Servers", should bring an alternate URL of "https://makeaseoquick.blogspot.com//search?q=".
Click on the iv links, inwards the paragraph at 1 time above, too compare the results - if you lot don't all the same encounter the seriousness here. Please. It's non a cosmetic detail.
This postal service "Custom Domain Redirection, And "A" Referral Servers", when linked equally "https://makeaseoquick.blogspot.com//search?q=", instead redirects to "http://nitecruzr.net/".
This postal service "Custom Domain Redirection, And "A" Referral Servers", when linked equally "https://makeaseoquick.blogspot.com//search?q=", instead redirects to "https://nitecruzr.net/".
Note that this weblog does non all the same purpose "HTTPS Redirect", then if you lot click on a link to "Custom Domain Redirection, And "A" Referral Servers" you lot volition encounter " ".
Here's a diagnosed illustration of the problem.
Here's a an illustration of this employment - diagnosed using a previous postal service blogging.nitecruzr.net/2016/08/delete-permanently-means-delete.html
A normal redirect - to "blogging.nitecruzr.net/2016/08/delete-permanently-means-delete.html"
https://makeaseoquick.blogspot.com//search?q=
HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Expires: Mon, 23 April 2018 03:25:09 GMT
Date: Mon, 23 April 2018 03:25:09 GMT
Cache-Control: private, max-age=0
Last-Modified: Mon, 23 April 2018 03:23:01 GMT
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Server: GSE
Accept-Ranges: none
Vary: Accept-Encoding
Transfer-Encoding: chunked
A broken redirect - to "blogging.nitecruzr.net"
https://makeaseoquick.blogspot.com//search?q=
HTTP/1.1 301 Moved Permanently
Location: http://blogging.nitecruzr.net
Date: Mon, 23 April 2018 03:23:18 GMT
Content-Type: text/html; charset=UTF-8
Server: ghs
Content-Length: 226
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
http://blogging.nitecruzr.net
HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Expires: Mon, 23 April 2018 03:23:19 GMT
Date: Mon, 23 April 2018 03:23:19 GMT
Cache-Control: private, max-age=0
Last-Modified: Mon, 23 April 2018 03:23:01 GMT
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Server: GSE
Accept-Ranges: none
Vary: Accept-Encoding
Transfer-Encoding: chunked
Unfortunately, roughly weblog owners are observing that redirection of a specific root URL - perhaps a custom landing page, or a specific postal service advertised using the root URL - appears to atomic number 82 exclusively to the dwelling identify page of the published blog.
This is a employment amongst domain / website design, inwards general - too amongst Blogger custom domain design, inwards particular.
The domain root to published URL (for most blogs, the "www" host) appears to purpose a version of frame forwarding, amongst roughly blogs beingness reported.
I never recommend using Frame Forwarding, inwards the custom domain DNS setup.
One of the disadvantages of frame forwarding is that redirects using frame forwarding driblet the postal service URL.
We've been seeing this employment reported, for several years.
The problem, rarely - simply non never - reported, started several years ago. This was earlier HTTPS for BlogSpot - too fifty-fifty further earlier HTTPS for custom domains - was rolled out.
This was before long afterwards nosotros started observing other problems involved, inwards the deployment of HTTPS.
The get-go HTTPS number was reported inwards 2014. HTTPS for BlogSpot was rolled out inwards 2015.
Related:
I'm betting nosotros get-go saw reports of the postal service URL beingness lost, inwards the ""http://xxxxxxx.whatever.com/whatever.html" -> ... -> "https://www.whatever.com"" was perhaps ii years ago. During deployment of HTTPS.
My approximate is that Blogger Engineers upgraded the domain root servers ("A" address) redirection code, to back upwardly HTTPS - too made a occupation concern conclusion to purpose frame forwarding.
From what I've seen of Blogger Engineering inwards full general - too custom domain pattern inwards exceptional - I am convinced that if they decided that frame forwarding is necessary, it's necessary. Until they tin right the problem, that is. My advice to every domain possessor to not purpose registrar supplied frame forwarding inwards the domain DNS, notwithstanding.
I tin exclusively promise that nosotros volition encounter this employment corrected, this decade. Remain optimistic - too written report the problem, when it tin hold upwardly identified.
It appears that roughly of the #Blogger custom domain "A" address cry servers are using "Frame Forwarding", instead of "Referral", to redirect the domain root to the published URL. Frame forwarding strips away the postal service address part of the URL - leaving exclusively the domain root.
Some weblog owners purpose the domain root to advertise their weblog posts - too are seeing exclusively the weblog dwelling identify page, instead of the private posts, when linking to the posts.
https://productforums.google.com/d/topic/blogger/NtQHoVNJ5PM/discussion
https://productforums.google.com/d/topic/blogger/pePwPhr_H-Y/discussion
https://productforums.google.com/forum/#!category-topic/blogger/pePwPhr_H-Y
https://productforums.google.com/forum/#!category-topic/blogger/nr-cIIgjBGg
