Ssl Together With The Www Alias Of Blogspot.Com
Wednesday, October 2, 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 every bit my BlogSpot mirror spider web log "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 encounter the problem, when viewing "https://www.blogger-status-for-real.blogspot.com/". The occupation manifestly involves the SSL certificate for "blogspot.com", which does non include the "www" aliase for the subdomains (such every bit "blogger-status-for-real.blogspot.com").
This month, Blogger decided to drib back upwardly for the "www" alias of "blogspot.com", when using SSL.
This agency that you lot tin accept either SSL for your "blogspot.com" published spider web log - or you lot tin allow your spider web log endure referenced using the "www" alias - but you lot cannot accept both. "https://www.blogger-status-for-real.blogspot.com/" volition but non endure available.
Nobody tin access my exam spider web log - without precisely about scary decisions - in addition to extra work.
Influenza A virus subtype H5N1 spider web log amongst an invalid certificate, when SSL access is attempted, tin endure 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 spider web log is in that place - if you lot expect for it. How many would endure readers volition willingly connect to the dangerous non SSL connection?
If the spider web log uses HSTS, instead of HTTPS, a connexion volition non endure 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 purpose HSTS won't endure accessible, period, insecurely.
If you're going to offering SSL access to your blog, your readers won't endure happy, using the "www" alias - if the alias works, at all. You'll necessitate 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 every bit my BlogSpot mirror spider web log "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
Related
This agency that you lot tin accept either SSL for your "blogspot.com" published spider web log - or you lot tin allow your spider web log endure referenced using the "www" alias - but you lot cannot accept both. "https://www.blogger-status-for-real.blogspot.com/" volition but non endure available.
Nobody tin access my exam spider web log - without precisely about scary decisions - in addition to extra work.
Influenza A virus subtype H5N1 spider web log amongst an invalid certificate, when SSL access is attempted, tin endure 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 spider web log is in that place - if you lot expect for it. How many would endure readers volition willingly connect to the dangerous non SSL connection?
If the spider web log uses HSTS, instead of HTTPS, a connexion volition non endure 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 purpose HSTS won't endure accessible, period, insecurely.
If you're going to offering SSL access to your blog, your readers won't endure happy, using the "www" alias - if the alias works, at all. You'll necessitate to purpose the base BlogSpot URL - instead of the "www" alias of the BlogSpot URL.
