Ssl As Well As The Www Alias Of Blogspot.Com
Wednesday, October 23, 2019
Edit
Last month, nosotros observed that SSL, though mostly available for blogs published to "blogspot.com", did non operate for all such blogs.
Owners of blogs who used the "www" alias of "blogspot.com", such equally my BlogSpot mirror weblog "https://blogger-status-for-real.blogspot.com/", reported annoying mistake messages, when trying to access the "www" alias of the blog, using SSL.
For my BlogSpot mirror blog, you'll run into the problem, when viewing "https://www.blogger-status-for-real.blogspot.com/". The occupation patently involves the SSL certificate for "blogspot.com", which does non include the "www" aliase for the subdomains (such equally "blogger-status-for-real.blogspot.com").
This month, Blogger decided to drib back upwards for the "www" alias of "blogspot.com", when using SSL.
This way that yous tin convey either SSL for your "blogspot.com" published weblog - or yous tin allow your weblog live on referenced using the "www" alias - but yous cannot convey both. "https://www.blogger-status-for-real.blogspot.com/" volition but non live on available.
Nobody tin access my exam weblog - without or in addition to then scary decisions - in addition to extra work.
Influenza A virus subtype H5N1 weblog amongst an invalid certificate, when SSL access is attempted, tin live on accessed - but non using SSL. The browser, that the reader is using, volition non connect to a website amongst an invalid certificate, using SSL.
The link to the weblog is at that spot - if yous await for it. How many would live on readers volition willingly connect to the dangerous non SSL connection?
If the weblog uses HSTS, instead of HTTPS, a connexion volition non live on available, period.
This is my mirror blog. It, too, is non accessible using SSL.
My mirror blog, however, uses HSTS - in addition to HSTS does non offering an insecure access option. Blogs which role HSTS won't live on accessible, period, insecurely.
If you're going to offering SSL access to your blog, your readers won't live on happy, using the "www" alias - if the alias works, at all. You'll need to role the base BlogSpot URL - instead of the "www" alias of the BlogSpot URL.
Owners of blogs who used the "www" alias of "blogspot.com", such equally my BlogSpot mirror weblog "https://blogger-status-for-real.blogspot.com/", reported annoying mistake messages, when trying to access the "www" alias of the blog, using SSL.
Your connexion is non private
For my BlogSpot mirror blog, you'll run into the problem, when viewing "https://www.blogger-status-for-real.blogspot.com/". The occupation patently involves the SSL certificate for "blogspot.com", which does non include the "www" aliase for the subdomains (such equally "blogger-status-for-real.blogspot.com").
This month, Blogger decided to drib back upwards for the "www" alias of "blogspot.com", when using SSL.
This way that yous tin convey either SSL for your "blogspot.com" published weblog - or yous tin allow your weblog live on referenced using the "www" alias - but yous cannot convey both. "https://www.blogger-status-for-real.blogspot.com/" volition but non live on available.
Nobody tin access my exam weblog - without or in addition to then scary decisions - in addition to extra work.
Influenza A virus subtype H5N1 weblog amongst an invalid certificate, when SSL access is attempted, tin live on accessed - but non using SSL. The browser, that the reader is using, volition non connect to a website amongst an invalid certificate, using SSL.
The link to the weblog is at that spot - if yous await for it. How many would live on readers volition willingly connect to the dangerous non SSL connection?
If the weblog uses HSTS, instead of HTTPS, a connexion volition non live on available, period.
This is my mirror blog. It, too, is non accessible using SSL.
My mirror blog, however, uses HSTS - in addition to HSTS does non offering an insecure access option. Blogs which role HSTS won't live on accessible, period, insecurely.
If you're going to offering SSL access to your blog, your readers won't live on happy, using the "www" alias - if the alias works, at all. You'll need to role the base BlogSpot URL - instead of the "www" alias of the BlogSpot URL.