SSL has been an option, for BlogSpot published blogs, since late last year - and we still see occasional questions, in Blogger Help Forum: Get Help with an Issue, about its use.
Until HTTPS availability, for all Internet content and services, becomes a consistent reality, there will be problems with Blogger blogs - and confusion, as in the example.
Custom domain publishing is the most vulnerable Blogger feature, with blogs using "HTTPS Redirect". It's not the only possible complication, though.
Some blog owners will be better off, not enabling "HTTPS Redirect" - or if enabled, they will need to disable it.
HTTPS Redirect can be easily disabled.
"HTTPS Redirect" is not difficult, to disable. Go to the dashboard Settings - Basic page.
Click on "Yes".
Select "No".
And, the option is disabled.
And the owner won't see the confusing "Fix" / "Dismiss" options.
Now, you can publish the blog, to a custom domain. With "HTTPS Availability" not optional, blogs, with essential features that don't provide SSL, will still have unsatisfied readers who will demand HTTPS.
Some blogs would be better off with "HTTPS Availability" as an option.
You cannot eliminate all confusion, until SSL is uniformly available.
I will note, however, that disabling the redirection will not eliminate reader concern, from "Mixed Content" alerts - nor will it prevent owner confusion, from Post Editor warnings. As long as SSL is (may be) involved - automatic redirect or not - and until every Internet feature and service uses SSL consistently - there is going to be some confusion.
Some #Blogger blog owners will need to disable the "HTTPS Redirect" option, to publish their blogs as they need. Right now, "HTTPS Redirect" is an option - and "HTTPS Availability" needs to be an option also.
When I saved my post, I saw the error messageThis blog owner will be better off, with "HTTPS Redirect" disabled.This page contains HTTP resources which may cause mixed content affecting security and user experience if blog is viewed over HTTPS.I clicked "Fix" - and the error message went away. Should I have to go back and "fix" all my old blog posts, this way?
Until HTTPS availability, for all Internet content and services, becomes a consistent reality, there will be problems with Blogger blogs - and confusion, as in the example.
Custom domain publishing is the most vulnerable Blogger feature, with blogs using "HTTPS Redirect". It's not the only possible complication, though.
Some blog owners will be better off, not enabling "HTTPS Redirect" - or if enabled, they will need to disable it.
HTTPS Redirect can be easily disabled.
"HTTPS Redirect" is not difficult, to disable. Go to the dashboard Settings - Basic page.
Click on "Yes".
Select "No".
And, the option is disabled.
Now, you can publish the blog, to a custom domain. With "HTTPS Availability" not optional, blogs, with essential features that don't provide SSL, will still have unsatisfied readers who will demand HTTPS.
Some blogs would be better off with "HTTPS Availability" as an option.
You cannot eliminate all confusion, until SSL is uniformly available.
I will note, however, that disabling the redirection will not eliminate reader concern, from "Mixed Content" alerts - nor will it prevent owner confusion, from Post Editor warnings. As long as SSL is (may be) involved - automatic redirect or not - and until every Internet feature and service uses SSL consistently - there is going to be some confusion.
Some #Blogger blog owners will need to disable the "HTTPS Redirect" option, to publish their blogs as they need. Right now, "HTTPS Redirect" is an option - and "HTTPS Availability" needs to be an option also.
Comments
Thanks for the question. From what I can tell, as long as SSL access is available - forced redirect or not, some blog features will lead to "mixed content" - and to the alerts. Forcing the redirect simply makes the alerts more likely.