Custom Domains As Well As Https Redirection Code
Sunday, November 2, 2014
Edit
As most of us know, Blogger HTTPS back upwards does non include custom domain publishing.
The advantages offered past times HTTPS access are widely advertised - as well as bring led to envy betwixt weblog owners who issue to custom domains, as well as native BlogSpot weblog owners proudly advertising their novel HTTPS connectivity.
Long ago, nosotros saw perhaps malicious code which helps our readers avoid using province code aliases, to read our blogs from an aliased country. Recently, in that place was dodgy code which blocked HTTPS mode, to read a customised blog.
Now, nosotros bring custom code to strength HTTPS access, for BlogSpot published blogs.
Along alongside providing code to assist weblog owners avoid province local domain aliasing, to a greater extent than or less marginally helpful hackers are providing code to assist weblog owners strength reader access to HTTPS.
Some weblog owners e'er wanted HTTPS to locomote used, to access their blog.
Some weblog owners wanted their readers e'er using HTTPS to access their blogs, earlier forced HTTPS access became an option. They Googled, as well as found, semi helpful hackers who render clever code to strength the "HTTP --> HTTPS" redirection.
This is clever code - when solely BlogSpot access is involved. When yous add together BlogSpot to custom domain redirection, it becomes to a greater extent than or less other "404".
Adding this clever code is an first-class solution - until the weblog possessor forgets most it, as well as later upgrades to a non BlogSpot custom domain.
With a custom domain published blog, the redirection becomes a problem.
The added code contains no exception to permit custom domain published blogs to stay inward HTTP mode. When accessing an otherwise properly setup custom domain published blog, from a reader using the "blogspot.com" URL, this prevents the BlogSpot to domain redirect from operating.
BlogSpot URLs, which should redirect to the HTTP published custom domain URL, instead redirect to a non existent HTTPS URL - as well as final result inward to a greater extent than or less other "404". As the custom domain URL becomes to a greater extent than unremarkably used for a late published blog, confusion increases when the rarer BlogSpot URL reference is encountered.
The work involves dual redirection - to "https:" mode, as well as to the custom domain.
After painful work diagnosis, nosotros honour the clever redirection code buried inward template HTML - as well as nosotros catch that the weblog reader is starting from the BlogSpot URL, as well as using the BlogSpot to domain redirection, to access the blog.
With weblog access redirected to "https:" mode, therefore after to the custom domain URL, the readers sees a "404" - because the custom domain URL is non available every bit "https:" content.
This work volition snuff it increasingly rarer - but non extinct.
As self caused custom domain victims snuff it rarer, this agency of breaking ones ain weblog volition snuff it to a greater extent than obscure - as well as it's probable that to a greater extent than or less cases volition go, unsolved. This volition locomote similar to the work of un migrated classic templates, which has increasingly less experienced support.
If yous must install unsupported template tweaks into your template - consider the long term effects. Learn to recognise a work that yous bring caused, to your ain blog.
Not every helper volition realise that yous bring added custom redirection code - as well as when looking at the work code, when a work is reported, volition recognise it for what it is. Your work may stay your work - at least, until Blogger Engineering completes Blogger SSL integration (may this orbit soon).
Some weblog owners bring added clever HTTP to HTTPS redirection code, acquired from helpful 3rd political party providers, installed inward the template. When later publishing a weblog to a custom domain, this code volition foreclose proper weblog access - as well as every bit installed, may non locomote easily recognised.
https://productforums.google.com/forum/#!category-topic/blogger/bl5W39BKX4U
The advantages offered past times HTTPS access are widely advertised - as well as bring led to envy betwixt weblog owners who issue to custom domains, as well as native BlogSpot weblog owners proudly advertising their novel HTTPS connectivity.
Long ago, nosotros saw perhaps malicious code which helps our readers avoid using province code aliases, to read our blogs from an aliased country. Recently, in that place was dodgy code which blocked HTTPS mode, to read a customised blog.
Now, nosotros bring custom code to strength HTTPS access, for BlogSpot published blogs.
Along alongside providing code to assist weblog owners avoid province local domain aliasing, to a greater extent than or less marginally helpful hackers are providing code to assist weblog owners strength reader access to HTTPS.
Some weblog owners e'er wanted HTTPS to locomote used, to access their blog.
Some weblog owners wanted their readers e'er using HTTPS to access their blogs, earlier forced HTTPS access became an option. They Googled, as well as found, semi helpful hackers who render clever code to strength the "HTTP --> HTTPS" redirection.
<script type='text/javascript'> $(document).ready(function() { $("a[href^='http://']").each( function(){ if(this.href.indexOf(location.hostname) == -1) { $(this).attr('target', '_blank'); } } ); $("a[href^='https://']").each function(){ if(this.href.indexOf(location.hostname) == -1) { $(this).attr('target', '_blank'); } } ); }); </script>
Adding this clever code is an first-class solution - until the weblog possessor forgets most it, as well as later upgrades to a non BlogSpot custom domain.
With a custom domain published blog, the redirection becomes a problem.
The added code contains no exception to permit custom domain published blogs to stay inward HTTP mode. When accessing an otherwise properly setup custom domain published blog, from a reader using the "blogspot.com" URL, this prevents the BlogSpot to domain redirect from operating.
BlogSpot URLs, which should redirect to the HTTP published custom domain URL, instead redirect to a non existent HTTPS URL - as well as final result inward to a greater extent than or less other "404". As the custom domain URL becomes to a greater extent than unremarkably used for a late published blog, confusion increases when the rarer BlogSpot URL reference is encountered.
My weblog has been using the domain URL for months, why is this happening now?
The work involves dual redirection - to "https:" mode, as well as to the custom domain.
After painful work diagnosis, nosotros honour the clever redirection code buried inward template HTML - as well as nosotros catch that the weblog reader is starting from the BlogSpot URL, as well as using the BlogSpot to domain redirection, to access the blog.
With weblog access redirected to "https:" mode, therefore after to the custom domain URL, the readers sees a "404" - because the custom domain URL is non available every bit "https:" content.
This work volition snuff it increasingly rarer - but non extinct.
As self caused custom domain victims snuff it rarer, this agency of breaking ones ain weblog volition snuff it to a greater extent than obscure - as well as it's probable that to a greater extent than or less cases volition go, unsolved. This volition locomote similar to the work of un migrated classic templates, which has increasingly less experienced support.
If yous must install unsupported template tweaks into your template - consider the long term effects. Learn to recognise a work that yous bring caused, to your ain blog.
Not every helper volition realise that yous bring added custom redirection code - as well as when looking at the work code, when a work is reported, volition recognise it for what it is. Your work may stay your work - at least, until Blogger Engineering completes Blogger SSL integration (may this orbit soon).
Some weblog owners bring added clever HTTP to HTTPS redirection code, acquired from helpful 3rd political party providers, installed inward the template. When later publishing a weblog to a custom domain, this code volition foreclose proper weblog access - as well as every bit installed, may non locomote easily recognised.
https://productforums.google.com/forum/#!category-topic/blogger/bl5W39BKX4U