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

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

Closed
Bisaloo opened this issue Jul 4, 2019 · 2 comments
Closed

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

Bisaloo opened this issue Jul 4, 2019 · 2 comments
Labels
broken MCB EASE Encrypt all sites eligible (#16985)

Comments

@Bisaloo
Copy link
Collaborator

Bisaloo commented Jul 4, 2019

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.

@Bisaloo Bisaloo added the EASE Encrypt all sites eligible (#16985) label Jul 4, 2019
@pipboy96
Copy link
Contributor

pipboy96 commented Jul 5, 2019

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?

@pipboy96
Copy link
Contributor

pipboy96 commented Jul 5, 2019

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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
broken MCB EASE Encrypt all sites eligible (#16985)
Projects
None yet
Development

No branches or pull requests

3 participants