News for hackers. Stuff that matters.
Re:Forcing Wordpress sites to use https even when not directed by michaelt on Thursday July 23, 2015 @07:44AM (#9935080)
Forgive my ignorance, but why would a browser need to say that it prefers https? Doesn't that go without saying nowerdays?

Surely only the most obscure, ancient legacy systems would have problems with being redirected to https?

Re:Forcing Wordpress sites to use https even when not directed by ricogallo on Thursday July 23, 2015 @07:54AM (#9935114)
Indeed, but you can see that a bunch of Wordpress sites are obscure, ancient and insecure by default.
Re:Forcing Wordpress sites to use https even when not directed by martius on Thursday July 23, 2015 @08:02AM (#9935152)
He's talking about a client not supporting HTTPS.

A client may have reasons to prefer HTTP over HTTPS: perfs, plaintext for debug, etc. It's hard to assume that "HTTPS should be the default" in any circumstance.

I'm not sure the wordpress sites are to blame here (for once): SSL isn't free to deploy (yet).

Re:Forcing Wordpress sites to use https even when not directed by uxp on Thursday July 23, 2015 @12:19PM (#9936720)
SSL is free to deploy: https://www.startssl.com?app=12

If you have a site that gets enough traffic that you need a better supported or more validated certificate, then I'm sure the $40/yr for a cheapass godaddy cert is worth the money.

Re:Forcing Wordpress sites to use https even when not directed by martius on Thursday July 23, 2015 @08:02PM (#9939266)
Assuming you have time and knowledge to do it. Assuming you own the domain or at least are able to access to its DNS records. Assuming you can use SNI (and all your visitors too) or have your own IPv4 address. Assuming $40 is free...

No, even a free certificate doesn't mean that deploying ssl is free.