Https Availability For All Blogspot.Com Blogs

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

All "blogspot.com" published blogs will immediately offering HTTPS connectivity, to the reader. The choice, offered to the weblog owner, is immediately whether to forcefulness every reader to operate SSL - in addition to the dashboard alternative is immediately labeled "HTTPS Redirect".

You tin forcefulness your readers to operate SSL, to access your weblog - simply volition that brand them to a greater extent than secure?

Every weblog volition offering SSL connectivity, to readers who operate "HTTPS:" URLs.


The dashboard alternative is immediately "HTTPS Redirect".




The selection is immediately whether to forcefulness "HTTPS:" upon each reader - or let to a greater extent than or less to overstep along to read, using "HTTP:".



If y'all pick out HTTPS Redirect, y'all volition live on limiting your reader population.

Some readers access our blogs, yesteryear using costless proxy servers - in addition to well-nigh proxy servers, when they offering HTTPS, offering it every bit a premium (with a paid subscription). You are entitled to ask everybody to operate SSL, if y'all wishing - simply y'all may meet reader activeness drop, every bit readers using costless proxies detect other blogs in addition to websites to read.


Everybody volition meet the "HTTPS:" alias - amongst "HTTPS Redirect" fix to "Yes".



My personal favourite connectivity diagnostic tool, Rex Swain HTTP Viewer, won't piece of occupation amongst blogs that alone back upwardly "HTTPS:" connectivity.

http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://nitecruzr-test-ssl.blogspot.com/&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7834.70.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/49.0.2623.112+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=AUTO


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



The "www" alias of a "blogspot.com" published weblog will non work, using SSL.


Using the "www" alias, of a "blogspot.com" URL, volition non piece of occupation - amongst "HTTPS Redirect" fix to "Yes".



Forcing SSL volition non brand your blogs readers to a greater extent than secure.

Use of "HTTPS Redirect", spell nominally making your readers to a greater extent than secure, volition bound access to your blog.

  • Readers, using proxy servers, may non live on able to access your blog.
  • Diagnostics of weblog problems, using proxy servers, volition live on limited.
  • Readers who bookmarked your blog, using the "www" alias, volition non live on able to access it.
  • Readers who are vulnerable to hijacking, when using "HTTP:", volition non access your blog.

Offering SSL connectivity is expert for everybody - simply empathise the limitations.

Enjoy offering SSL connectivity - in addition to improved search engine reputation. But maintain it inwards perspective.

People who explicitly operate "HTTP:" to access your blog, in addition to are vulnerable to hijacking, volition meet an imposters weblog - fifty-fifty if your weblog forces them to operate SSL. Only people who explicitly operate "HTTPS:", to access your blog, volition predictably meet your weblog - in addition to they won't create goodness from beingness forced to operate SSL.



As #Blogger continues the rollout of SSL to "blogspot.com" published blogs, they accept changed the HTTPS option. All blogs which back upwardly SSL volition offering "HTTPS:" connectivity, in addition to the alternative volition live on to let explicit access, using "HTTP:".

You may create good to reckon what benefits y'all get, from forcing your readers to operate SSL to access your blog.

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel