Please Google, Don’t shame HTTP (yet)

You may also like...

2 Responses

  1. You’re probably right, Jon. On a lark, I decided to count how many of my tabs in this window were http rather than https. It was 15 out of 34, one ironically was the blog you linked to about Comcast hijacking non-https traffic. Do you advise using something like the chrome https-everywhere extension?

    • Jon says:

      I think the “HTTPS Everywhere” extensions are a good thing. They effectively switch the default from loading http to loading https. It’s be nice is browsers did that with a quick fall back to http, but that’d probably break a lot. The double irony to that blog post is that his site is HTTPS available, its just not setup to 301. Maybe that could be the next iteration of features for browsers/extensions: Load site on http as normal, check in background if its https also works with same/similar content? If yes, then swap the user over to https silently.

      Its really unfortunate that a lot of big websites still don’t HTTPS by default. Engadget, Gizmodo, Slashdot, TechCrunch, CNN, NYTimes… well, you get the idea.

Leave a Reply to Jon Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: