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.

Use platform="mixedcontent" rulesets when EASE is enabled #18160

Closed

Description

@Bisaloo

Type: feature request

It would be useful to use the platform="mixedcontent" rulesets with EASE to increase the number of functional websites.

You can test this by visiting http://legorafi.fr (with EASE enabled) even when there is a rule (with platform="mixedcontent") that should handle this case:

<rule from="^http://legorafi\.fr/"
to="https://www.legorafi.fr/" />

Because EASE also sends the upgrade-insecure-requests header, platform="mixedcontent" rulesets should not cause any issues in most cases.

Activity

  1. added
    EASEEncrypt all sites eligible (#16985)
    on Jul 4, 2019
  2. pipboy96 commented on Jul 5, 2019

    @pipboy96
    Contributor

    Nice one! I also noticed EASE can fix mixed content issues. Can we also do the opposite and allow some rulesets to attempt such fix even if user does not have EASE on?

  3. pipboy96 commented on Jul 5, 2019

    @pipboy96
    Contributor

    I think we can also bypass MCB even if further redirects are required by using upgrade-insecure-requests and then doing https => https redirect.

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

    EASEEncrypt all sites eligible (#16985)broken MCB

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions