Custom Domains Too Https Redirection Code
Wednesday, October 12, 2016
Edit
As most of us know, Blogger HTTPS back upwards does non include custom domain publishing.
The advantages offered yesteryear HTTPS access are widely advertised - too convey led to envy betwixt weblog owners who issue to custom domains, too native BlogSpot weblog owners proudly advertising their novel HTTPS connectivity.
Long ago, nosotros saw perchance 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 convey custom code to forcefulness HTTPS access, for BlogSpot published blogs.
Along alongside providing code to assist weblog owners avoid province local domain aliasing, about marginally helpful hackers are providing code to assist weblog owners forcefulness reader access to HTTPS.
Some weblog owners e'er wanted HTTPS to survive 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, too found, semi helpful hackers who render clever code to forcefulness the "HTTP --> HTTPS" redirection.
This is clever code - when exclusively BlogSpot access is involved. When y'all add together BlogSpot to custom domain redirection, it becomes about other "404".
Adding this clever code is an splendid solution - until the weblog possessor forgets most it, too 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 rest inwards 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 - too resultant inwards about 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 employment involves dual redirection - to "https:" mode, too to the custom domain.
After painful employment diagnosis, nosotros honor the clever redirection code buried inwards template HTML - too nosotros consider that the weblog reader is starting from the BlogSpot URL, too using the BlogSpot to domain redirection, to access the blog.
With weblog access redirected to "https:" mode, hence later to the custom domain URL, the readers sees a "404" - because the custom domain URL is non available equally "https:" content.
This employment volition decease increasingly rarer - but non extinct.
As self caused custom domain victims decease rarer, this means of breaking ones ain weblog volition decease to a greater extent than obscure - too it's probable that about cases volition go, unsolved. This volition survive similar to the employment of un migrated classic templates, which has increasingly less experienced support.
If y'all must install unsupported template tweaks into your template - consider the long term effects. Learn to recognise a employment that y'all convey caused, to your ain blog.
Not every helper volition realise that y'all convey added custom redirection code - too when looking at the employment code, when a employment is reported, volition recognise it for what it is. Your employment may rest your employment - at least, until Blogger Engineering completes Blogger SSL integration (may this come about soon).
Some weblog owners convey added clever HTTP to HTTPS redirection code, acquired from helpful 3rd political party providers, installed inwards the template. When later publishing a weblog to a custom domain, this code volition preclude proper weblog access - too equally installed, may non survive easily recognised.
https://productforums.google.com/forum/#!category-topic/blogger/bl5W39BKX4U
The advantages offered yesteryear HTTPS access are widely advertised - too convey led to envy betwixt weblog owners who issue to custom domains, too native BlogSpot weblog owners proudly advertising their novel HTTPS connectivity.
Long ago, nosotros saw perchance 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 convey custom code to forcefulness HTTPS access, for BlogSpot published blogs.
Along alongside providing code to assist weblog owners avoid province local domain aliasing, about marginally helpful hackers are providing code to assist weblog owners forcefulness reader access to HTTPS.
Some weblog owners e'er wanted HTTPS to survive 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, too found, semi helpful hackers who render clever code to forcefulness 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 splendid solution - until the weblog possessor forgets most it, too 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 rest inwards 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 - too resultant inwards about 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 employment involves dual redirection - to "https:" mode, too to the custom domain.
After painful employment diagnosis, nosotros honor the clever redirection code buried inwards template HTML - too nosotros consider that the weblog reader is starting from the BlogSpot URL, too using the BlogSpot to domain redirection, to access the blog.
With weblog access redirected to "https:" mode, hence later to the custom domain URL, the readers sees a "404" - because the custom domain URL is non available equally "https:" content.
This employment volition decease increasingly rarer - but non extinct.
As self caused custom domain victims decease rarer, this means of breaking ones ain weblog volition decease to a greater extent than obscure - too it's probable that about cases volition go, unsolved. This volition survive similar to the employment of un migrated classic templates, which has increasingly less experienced support.
If y'all must install unsupported template tweaks into your template - consider the long term effects. Learn to recognise a employment that y'all convey caused, to your ain blog.
Not every helper volition realise that y'all convey added custom redirection code - too when looking at the employment code, when a employment is reported, volition recognise it for what it is. Your employment may rest your employment - at least, until Blogger Engineering completes Blogger SSL integration (may this come about soon).
Some weblog owners convey added clever HTTP to HTTPS redirection code, acquired from helpful 3rd political party providers, installed inwards the template. When later publishing a weblog to a custom domain, this code volition preclude proper weblog access - too equally installed, may non survive easily recognised.
https://productforums.google.com/forum/#!category-topic/blogger/bl5W39BKX4U