Skip to main content

HTTPS Availability For All "" Blogs

The rollout of SSL, for "" published blogs, continues.

All "" published blogs will now offer HTTPS connectivity, to the reader. The choice, offered to the blog owner, is now whether to force every reader to use SSL - and the dashboard option is now labeled "HTTPS Redirect".

You can force your readers to use SSL, to access your blog - but will that make them more secure?

Every blog will offer SSL connectivity, to readers who use "HTTPS:" URLs.

The dashboard option is now "HTTPS Redirect".

The choice is now whether to force "HTTPS:" upon each reader - or allow some to continue to read, using "HTTP:".

If you select HTTPS Redirect, you will be limiting your reader population.

Some readers access our blogs, by using free proxy servers - and most proxy servers, when they offer HTTPS, offer it as a premium (with a paid subscription). You are entitled to require everybody to use SSL, if you wish - but you may see reader activity drop, as readers using free proxies find other blogs and websites to read.

Everybody will see the "HTTPS:" alias - with "HTTPS Redirect" set to "Yes".

My personal favourite connectivity diagnostic tool, Rex Swain HTTP Viewer, won't work with blogs that only support "HTTPS:" connectivity.,+like+Gecko)+Chrome/49.0.2623.112+Safari/537.36&ref=

No "HTTP:" diagnostics, for "HTTPS:" redirected blogs.

The "www" alias of a "" published blog will not work, using SSL.

Using the "www" alias, of a "" URL, will not work - with "HTTPS Redirect" set to "Yes".

Forcing SSL will not make your blogs readers more secure.

Use of "HTTPS Redirect", while nominally making your readers more secure, will limit access to your blog.

  • Readers, using proxy servers, may not be able to access your blog.
  • Diagnostics of blog problems, using proxy servers, will be limited.
  • Readers who bookmarked your blog, using the "www" alias, will not be able to access it.
  • Readers who are vulnerable to hijacking, when using "HTTP:", will not access your blog.

Offering SSL connectivity is good for everybody - but understand the limitations.

Enjoy offering SSL connectivity - and improved search engine reputation. But keep it in perspective.

People who explicitly use "HTTP:" to access your blog, and are vulnerable to hijacking, will see an imposters blog - even if your blog forces them to use SSL. Only people who explicitly use "HTTPS:", to access your blog, will predictably see your blog - and they won't benefit from being forced to use SSL.

As #Blogger continues the rollout of SSL to "" published blogs, they have changed the HTTPS option. All blogs which support SSL will offer "HTTPS:" connectivity, and the option will be to allow explicit access, using "HTTP:".

You may do well to consider what benefits you get, from forcing your readers to use SSL to access your blog.


G. B. Miller said…
Personally, I use the https only with Facebook. Otherwise, I try to make things as easy as possible for my readers.
Chuck Croll said…
Hi G.B.,

Thanks for the feedback!

That makes sense - focus your efforts on specific targets. And, as I wrote just a few minutes ago, as you gain proficiency, use https: with more websites. Just change a bit at a time.

And wait for the next SSL upgrade, which will come soon enough.

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: