Securely connect to websites via https first by default, if not then, use http as fallback. This will prevent downgrade attacks.
I have a suggestion. I would like for browsers to connect securely via https first by default to websites. When the browser checks that https is not supported by the website, it should downgrade to http, so do invalid certificates. This will prevent downgrade attacks and make HSTS headers optional. Browsers for years have been connecting to http by default, which I feel is a security risk. A kind of design flaw. Is an option to connect to https first by default a good idea?
I have a suggestion. I would like for browsers to connect securely via https first by default to websites. When the browser checks that https is not supported by the website, it should downgrade to http, so do invalid certificates. This will prevent downgrade attacks and make HSTS headers optional. Browsers for years have been connecting to http by default, which I feel is a security risk. A kind of design flaw. Is an option to connect to https first by default a good idea?
All Replies (2)
You may submit suggestions to the developers here: https://input.mozilla.org/en-US/feedback
See:
- HTTPS Everywhere: http://www.eff.org/https-everywhere