1) If the user goes to http://www.example.com and https-finder checks wether we can rewrite it to https://www.example.com .
Pages often load content from third party pages or subdomains
like images.example.com or scripts.siteb.com.
We should check if we can rewrite these as well, and add it to example.coms rule in the first case or create a rule for the thirdparty page in the second case
2) The ssl redirect sometimes causes mixed-content warnings and/or ends up with a non trusted certificate (self-signed, not valid for the domain you try to access,expired).
Those kind of exceptions end up as exclusions,comments and flags in https-everywheres rulesets. It would be nice to add them automatically as well.
1) If the user goes to http://www.example.com and https-finder checks wether we can rewrite it to https://www.example.com . Pages often load content from third party pages or subdomains like images.example.com or scripts.siteb.com. We should check if we can rewrite these as well, and add it to example.coms rule in the first case or create a rule for the thirdparty page in the second case
2) The ssl redirect sometimes causes mixed-content warnings and/or ends up with a non trusted certificate (self-signed, not valid for the domain you try to access,expired). Those kind of exceptions end up as exclusions,comments and flags in https-everywheres rulesets. It would be nice to add them automatically as well.