You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Why is this not implemented? It's better than HTTP Nowhere because with this you can visit HTTP-sites, but while you're on HTTPS-sites you will only see content delivered over HTTPS so no mixed content whatsoever.
Okay, finally I have to admit you mean something else: Do you want to ad the behaviour of "upgrade-insecure-requests" to every website so it always tries to load the mixed content over HTTPS?
However a CSP which would look like upgrade-insecure-requests; block-all-mixed-content is actually contradictory, because upgrade-insecure-requests tells the browser to try HTTPS and block it if it does not work (or - respectively - fall back to the default behaviour) and block-all-mixed-content says the browser should instantly block all mixed content (which is the default for active mixed content, where "active" means all non-static [images] resources are affected).
So only upgrade-insecure-requests is the better choice as I do not know what browsers do when both directives are defined.
I did not know that upgrade-insecure-requests blocked HTTP-requests if the upgrade was not successful. So in that case the block-all-mixed-content is unnecessary in this manner.
Also, I don't know if it's a good idea to replace this with HTTP Nowhere. The CSP-header should be added (opt-in) on HTTPS-links. This will - like I wrote - block mixed content.
Activity
rugk commentedon Dec 5, 2015
duplicate of #2115 (okay, maybe not... this depends on what exactly you mean)
rugk commentedon Dec 5, 2015
As for why HTTPS Everywhere does not just tries HTTPS for every site in normal (not-http-blocking) mode here are more information: https://www.eff.org/https-everywhere/faq#faq-Why-use-a-whitelist-of-sites-that-support-HTTPS?-Why-can%27t-you-try-to-use-HTTPS-for-every-last-site,-and-only-fall-back-to-HTTP-if-it-isn%27t-available?
rugk commentedon Dec 5, 2015
Okay, finally I have to admit you mean something else: Do you want to ad the behaviour of "upgrade-insecure-requests" to every website so it always tries to load the mixed content over HTTPS?
However a CSP which would look like
upgrade-insecure-requests; block-all-mixed-contentis actually contradictory, becauseupgrade-insecure-requeststells the browser to try HTTPS and block it if it does not work (or - respectively - fall back to the default behaviour) andblock-all-mixed-contentsays the browser should instantly block all mixed content (which is the default for active mixed content, where "active" means all non-static [images] resources are affected).So only
upgrade-insecure-requestsis the better choice as I do not know what browsers do when both directives are defined.Related: https://scotthelme.co.uk/migrating-from-http-to-https-ease-the-pain-with-csp-and-hsts/
intchloe commentedon Dec 6, 2015
I did not know that
upgrade-insecure-requestsblocked HTTP-requests if the upgrade was not successful. So in that case theblock-all-mixed-contentis unnecessary in this manner.intchloe commentedon Dec 6, 2015
Also, I don't know if it's a good idea to replace this with HTTP Nowhere. The CSP-header should be added (opt-in) on HTTPS-links. This will - like I wrote - block mixed content.
rugk commentedon Dec 6, 2015
Just FYI: https://scotthelme.co.uk/migrating-from-http-to-https-ease-the-pain-with-csp-and-hsts/#comment-2395046331 😃
jeremyn commentedon Dec 27, 2017
@intchloe Thanks for your suggestion, however I'm closing this issue as a duplicate of issue #8506, which has more discussion.