Custom Domains In Addition To Https Redirection Code
Monday, March 4, 2013
Edit
As most of us know, Blogger HTTPS back upward does non include custom domain publishing.
The advantages offered yesteryear HTTPS access are widely advertised - together with bring led to envy betwixt weblog owners who set out to custom domains, together with 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, at that spot was dodgy code which blocked HTTPS mode, to read a customised blog.
Now, nosotros bring custom code to forcefulness HTTPS access, for BlogSpot published blogs.
Along amongst providing code to assist weblog owners avoid province local domain aliasing, roughly marginally helpful hackers are providing code to assist weblog owners forcefulness 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, together with found, semi helpful hackers who render clever code to forcefulness the "HTTP --> HTTPS" redirection.
This is clever code - when solely BlogSpot access is involved. When you lot add together BlogSpot to custom domain redirection, it becomes roughly other "404".
Adding this clever code is an fantabulous solution - until the weblog possessor forgets almost it, together with 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 - together with resultant inwards roughly other "404". As the custom domain URL becomes to a greater extent than ordinarily used for a late published blog, confusion increases when the rarer BlogSpot URL reference is encountered.
The work involves dual redirection - to "https:" mode, together with to the custom domain.
After painful work diagnosis, nosotros detect the clever redirection code buried inwards template HTML - together with nosotros reckon that the weblog reader is starting from the BlogSpot URL, together with using the BlogSpot to domain redirection, to access the blog.
With weblog access redirected to "https:" mode, together with thence later 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 teach increasingly rarer - but non extinct.
As self caused custom domain victims teach rarer, this agency of breaking ones ain weblog volition teach to a greater extent than obscure - together with it's probable that roughly cases volition go, unsolved. This volition locomote similar to the work of un migrated classic templates, which has increasingly less experienced support.
If you lot must install unsupported template tweaks into your template - consider the long term effects. Learn to recognise a work that you lot bring caused, to your ain blog.
Not every helper volition realise that you lot bring added custom redirection code - together with when looking at the work code, when a work is reported, volition recognise it for what it is. Your work may rest your work - at least, until Blogger Engineering completes Blogger SSL integration (may this laissez passer on off soon).
Some weblog owners bring added clever HTTP to HTTPS redirection code, acquired from helpful tertiary political party providers, installed inwards the template. When later publishing a weblog to a custom domain, this code volition foreclose proper weblog access - together with every bit installed, may non locomote easily recognised.
https://productforums.google.com/forum/#!category-topic/blogger/bl5W39BKX4U
The advantages offered yesteryear HTTPS access are widely advertised - together with bring led to envy betwixt weblog owners who set out to custom domains, together with 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, at that spot was dodgy code which blocked HTTPS mode, to read a customised blog.
Now, nosotros bring custom code to forcefulness HTTPS access, for BlogSpot published blogs.
Along amongst providing code to assist weblog owners avoid province local domain aliasing, roughly marginally helpful hackers are providing code to assist weblog owners forcefulness 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, together with 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 fantabulous solution - until the weblog possessor forgets almost it, together with 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 - together with resultant inwards roughly other "404". As the custom domain URL becomes to a greater extent than ordinarily 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, together with to the custom domain.
After painful work diagnosis, nosotros detect the clever redirection code buried inwards template HTML - together with nosotros reckon that the weblog reader is starting from the BlogSpot URL, together with using the BlogSpot to domain redirection, to access the blog.
With weblog access redirected to "https:" mode, together with thence later 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 teach increasingly rarer - but non extinct.
As self caused custom domain victims teach rarer, this agency of breaking ones ain weblog volition teach to a greater extent than obscure - together with it's probable that roughly cases volition go, unsolved. This volition locomote similar to the work of un migrated classic templates, which has increasingly less experienced support.
If you lot must install unsupported template tweaks into your template - consider the long term effects. Learn to recognise a work that you lot bring caused, to your ain blog.
Not every helper volition realise that you lot bring added custom redirection code - together with when looking at the work code, when a work is reported, volition recognise it for what it is. Your work may rest your work - at least, until Blogger Engineering completes Blogger SSL integration (may this laissez passer on off soon).
Some weblog owners bring added clever HTTP to HTTPS redirection code, acquired from helpful tertiary political party providers, installed inwards the template. When later publishing a weblog to a custom domain, this code volition foreclose proper weblog access - together with every bit installed, may non locomote easily recognised.
https://productforums.google.com/forum/#!category-topic/blogger/bl5W39BKX4U