Ssl As Well As The Www Alias Of Blogspot.Com
Tuesday, November 3, 2015
Edit
Last month, nosotros observed that SSL, though to a greater extent than oft than non available for blogs published to "blogspot.com", did non run 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 fault messages, when trying to access the "www" alias of the blog, using SSL.
For my BlogSpot mirror blog, you'll encounter the problem, when viewing "https://www.blogger-status-for-real.blogspot.com/". The work evidently 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 driblet back upward for the "www" alias of "blogspot.com", when using SSL.
This agency that yous tin convey either SSL for your "blogspot.com" published weblog - or yous tin permit your weblog locomote referenced using the "www" alias - but yous cannot convey both. "https://www.blogger-status-for-real.blogspot.com/" volition only non locomote available.
Nobody tin access my examination weblog - without or too thus scary decisions - too extra work.
Influenza A virus subtype H5N1 weblog alongside an invalid certificate, when SSL access is attempted, tin locomote accessed - but non using SSL. The browser, that the reader is using, volition non connect to a website alongside an invalid certificate, using SSL.
The link to the weblog is at that spot - if yous await for it. How many would locomote readers volition willingly connect to the dangerous non SSL connection?
If the weblog uses HSTS, instead of HTTPS, a connexion volition non locomote available, period.
This is my mirror blog. It, too, is non accessible using SSL.
My mirror blog, however, uses HSTS - too HSTS does non offering an insecure access option. Blogs which purpose HSTS won't locomote accessible, period, insecurely.
If you're going to offering SSL access to your blog, your readers won't locomote happy, using the "www" alias - if the alias works, at all. You'll need to purpose 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 fault 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 encounter the problem, when viewing "https://www.blogger-status-for-real.blogspot.com/". The work evidently 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 driblet back upward for the "www" alias of "blogspot.com", when using SSL.
This agency that yous tin convey either SSL for your "blogspot.com" published weblog - or yous tin permit your weblog locomote referenced using the "www" alias - but yous cannot convey both. "https://www.blogger-status-for-real.blogspot.com/" volition only non locomote available.
Nobody tin access my examination weblog - without or too thus scary decisions - too extra work.
Influenza A virus subtype H5N1 weblog alongside an invalid certificate, when SSL access is attempted, tin locomote accessed - but non using SSL. The browser, that the reader is using, volition non connect to a website alongside an invalid certificate, using SSL.
The link to the weblog is at that spot - if yous await for it. How many would locomote readers volition willingly connect to the dangerous non SSL connection?
If the weblog uses HSTS, instead of HTTPS, a connexion volition non locomote available, period.
This is my mirror blog. It, too, is non accessible using SSL.
My mirror blog, however, uses HSTS - too HSTS does non offering an insecure access option. Blogs which purpose HSTS won't locomote accessible, period, insecurely.
If you're going to offering SSL access to your blog, your readers won't locomote happy, using the "www" alias - if the alias works, at all. You'll need to purpose the base BlogSpot URL - instead of the "www" alias of the BlogSpot URL.