HTTPS Everywhere: interesting idea, terrible implementation

Last night I finally figured out why Amazon wouldn’t let me view inside books, it was because I still had HTTPS everywhere enabled for amazon.  It’s a neat idea to force your web session secure for sites that support it, but don’t make it easy.  Good in theory… in practice not so much.

When I finally figured out that it attempted to work with Amazon I noticed that I had disabled all the sites I actually use in the tool.  Twitter is rediculously slow under https, like 1 minute to load a page slow.  Google images aren’t searchable under https, so you don’t see it on the sidebar as an option.  Some of the facebook javascript wasn’t fetchable over https.  Wikipedia inbound search from google doesn’t work if it’s enabled.

It makes me wonder what part of the internet is used by the folks writing this addon, because it doesn’t seem to be the same part that I’m using.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s