@markosaric have you already stumbled in any sites that misbehave when you switch to https?
Several years ago, when https adoption was still spotty, my homepage required HTTP basic-auth on https. It was my way to separate read-only access from editing. Now I use a url prefix instead.
@codewiz haven't noticed any issues at all since enabling it this morning.
there was one website where it gave me a prompt that secure connection is not available and gave me option to visit via http or go back
that's why i mean that it should be enabled by default as it seems very safe and doesn't break much (or anything)
Well, you won't see any of my websites since I do NOT enable HTTPS when it's not needed.
I guess it's not a big issue to people from the rich western countries, but I want proxies to be able to cache the contents to improve accessibility over slow connections in poor countries.
And since I don't care profiling my visitors and do not distribute sensible contents, I wont waste energy on pointless cpu cicles.