Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Add CSP "upgrade-insecure-requests; block-all-mixed-content" #3343

Closed

Description

@intchloe

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.

Is there a reason behind this?

Activity

  1. rugk commented on Dec 5, 2015

    @rugk
    Contributor

    duplicate of #2115 (okay, maybe not... this depends on what exactly you mean)

  2. rugk commented on Dec 5, 2015

    @rugk
    Contributor

    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?

  3. rugk commented on Dec 5, 2015

    @rugk
    Contributor

    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.

    Related: https://scotthelme.co.uk/migrating-from-http-to-https-ease-the-pain-with-csp-and-hsts/

  4. intchloe commented on Dec 6, 2015

    @intchloe
    ContributorAuthor

    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.

  5. intchloe commented on Dec 6, 2015

    @intchloe
    ContributorAuthor

    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.

  6. jeremyn commented on Dec 27, 2017

    @jeremyn
    Contributor

    @intchloe Thanks for your suggestion, however I'm closing this issue as a duplicate of issue #8506, which has more discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions