Custom Domain Redirection, In Addition To A Referral Servers
Friday, October 10, 2014
Edit
One of the advantages of custom domain publishing, in addition to the domain root to published URL redirection, used to last transparent redirection of the URLs.
As Blogger weblog owners instruct to a greater extent than sophisticated alongside their blogs, in addition to custom abode pages (aka "landing pages"), instruct to a greater extent than popular, nosotros bring weblog owners alongside concerns virtually abode page access in addition to domain root redirection. We are likewise seeing concern alongside directly access to specific posts - alongside posts advertised, using the domain root URL.
In about cases, redirection solely shows the reader the weblog abode page, equally the commencement persuasion of the weblog - fifty-fifty alongside a specific postal service beingness linked inward 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://satriyoblog.blogspot.com//search?q=".
Click on the iv links, inward the paragraph at 1 time above, in addition to compare the results - if you lot don't however run across the seriousness here. Please. It's non a cosmetic detail.
This postal service "Custom Domain Redirection, And "A" Referral Servers", when linked equally "https://satriyoblog.blogspot.com//search?q=", instead redirects to "http://nitecruzr.net/".
This postal service "Custom Domain Redirection, And "A" Referral Servers", when linked equally "https://satriyoblog.blogspot.com//search?q=", instead redirects to "https://nitecruzr.net/".
Note that this weblog does non however role "HTTPS Redirect", in addition to thus if you lot click on a link to "Custom Domain Redirection, And "A" Referral Servers" you lot volition run across " ".
Here's a diagnosed representative of the problem.
Here's a an representative 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 abode page, using HTTPS.
Unfortunately, about weblog owners are observing that redirection of a specific root URL - perchance a custom landing page, or a specific postal service advertised using the root URL - appears to Pb solely to the abode page of the published blog.
This is a employment alongside domain / website design, inward general - in addition to alongside Blogger custom domain design, inward particular.
The domain root to published URL (for most blogs, the "www" host) appears to role a version of frame forwarding, alongside about blogs beingness reported.
I never recommend using Frame Forwarding, inward 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 - precisely non never - reported, started several years ago. This was earlier HTTPS for BlogSpot - in addition to fifty-fifty further earlier HTTPS for custom domains - was rolled out.
This was soon afterwards nosotros started observing other problems involved, inward the deployment of HTTPS.
The commencement HTTPS number was reported inward 2014. HTTPS for BlogSpot was rolled out inward 2015.
I'm betting nosotros commencement saw reports of the postal service URL beingness lost, inward the ""http://xxxxxxx.whatever.com/whatever.html" -> ... -> "https://www.whatever.com"" was perchance two years ago. During deployment of HTTPS.
My jurist is that Blogger Engineers upgraded the domain root servers ("A" address) redirection code, to back upward HTTPS - in addition to made a draw of piece of work organisation determination to role frame forwarding.
From what I've seen of Blogger Engineering inward full general - in addition to custom domain pattern inward exceptional - I am convinced that if they decided that frame forwarding is necessary, it's necessary. Until they tin laissez passer on the sack right the problem, that is. My advice to every domain possessor to not role registrar supplied frame forwarding inward the domain DNS, notwithstanding.
I tin laissez passer on the sack solely promise that nosotros volition run across this employment corrected, this decade. Remain optimistic - in addition to study the problem, when it tin laissez passer on the sack last identified.
It appears that about of the #Blogger custom domain "A" address hollo 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 share of the URL - leaving solely the domain root.
Some weblog owners role the domain root to advertise their weblog posts - in addition to are seeing solely the weblog abode 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 instruct to a greater extent than sophisticated alongside their blogs, in addition to custom abode pages (aka "landing pages"), instruct to a greater extent than popular, nosotros bring weblog owners alongside concerns virtually abode page access in addition to domain root redirection. We are likewise seeing concern alongside directly access to specific posts - alongside posts advertised, using the domain root URL.
In about cases, redirection solely shows the reader the weblog abode page, equally the commencement persuasion of the weblog - fifty-fifty alongside a specific postal service beingness linked inward 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://satriyoblog.blogspot.com//search?q=".
Click on the iv links, inward the paragraph at 1 time above, in addition to compare the results - if you lot don't however run across the seriousness here. Please. It's non a cosmetic detail.
This postal service "Custom Domain Redirection, And "A" Referral Servers", when linked equally "https://satriyoblog.blogspot.com//search?q=", instead redirects to "http://nitecruzr.net/".
This postal service "Custom Domain Redirection, And "A" Referral Servers", when linked equally "https://satriyoblog.blogspot.com//search?q=", instead redirects to "https://nitecruzr.net/".
Note that this weblog does non however role "HTTPS Redirect", in addition to thus if you lot click on a link to "Custom Domain Redirection, And "A" Referral Servers" you lot volition run across " ".
Here's a diagnosed representative of the problem.
Here's a an representative 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://satriyoblog.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://satriyoblog.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, about weblog owners are observing that redirection of a specific root URL - perchance a custom landing page, or a specific postal service advertised using the root URL - appears to Pb solely to the abode page of the published blog.
This is a employment alongside domain / website design, inward general - in addition to alongside Blogger custom domain design, inward particular.
The domain root to published URL (for most blogs, the "www" host) appears to role a version of frame forwarding, alongside about blogs beingness reported.
I never recommend using Frame Forwarding, inward 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 - precisely non never - reported, started several years ago. This was earlier HTTPS for BlogSpot - in addition to fifty-fifty further earlier HTTPS for custom domains - was rolled out.
This was soon afterwards nosotros started observing other problems involved, inward the deployment of HTTPS.
The commencement HTTPS number was reported inward 2014. HTTPS for BlogSpot was rolled out inward 2015.
I'm betting nosotros commencement saw reports of the postal service URL beingness lost, inward the ""http://xxxxxxx.whatever.com/whatever.html" -> ... -> "https://www.whatever.com"" was perchance two years ago. During deployment of HTTPS.
My jurist is that Blogger Engineers upgraded the domain root servers ("A" address) redirection code, to back upward HTTPS - in addition to made a draw of piece of work organisation determination to role frame forwarding.
From what I've seen of Blogger Engineering inward full general - in addition to custom domain pattern inward exceptional - I am convinced that if they decided that frame forwarding is necessary, it's necessary. Until they tin laissez passer on the sack right the problem, that is. My advice to every domain possessor to not role registrar supplied frame forwarding inward the domain DNS, notwithstanding.
I tin laissez passer on the sack solely promise that nosotros volition run across this employment corrected, this decade. Remain optimistic - in addition to study the problem, when it tin laissez passer on the sack last identified.
It appears that about of the #Blogger custom domain "A" address hollo 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 share of the URL - leaving solely the domain root.
Some weblog owners role the domain root to advertise their weblog posts - in addition to are seeing solely the weblog abode 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