1
0
Fork 0
mirror of https://github.com/gorhill/uMatrix.git synced 2024-06-02 18:34:52 +12:00

Updated Per scope switches (markdown)

gorhill 2014-11-22 03:52:09 -08:00
parent 801bef5883
commit 108520be7c

@ -34,7 +34,7 @@ Also, notice that now I use the term "spoofing". Whereas before the referrer str
### Strict HTTPS
**Edit 2014-11-21:** After I updated to Chromium 38 yesterday, I just found out that now apparently Chromium forbids mixed content by default. When there is mixed content on a web page, a little shield icon will appear in the address bar, and a user may click on it to load the content which was forbidden from loading natively by the browser. This is great, and this kind of render the new _"Strict HTTPS"_ switch here useless. I still have to see if does this completely for all types of requests, but I expect it to be the case (tell me if you find out it still can happen). Given this, I may remove the _"Strict HTTPS"_ switch before release if it ends up not having a purpose anymore.
**Edit 2014-11-21:** After I updated to Chromium 38 yesterday, I just found out that now apparently Chromium forbids mixed content by default. When there is mixed content on a web page, a little shield icon will appear in the address bar, and a user may click on it to load the content which was forbidden from loading natively by the browser. However, as [investigated by a user](https://github.com/gorhill/uMatrix/issues/67), this applies **only** to request of type `script`.
First, if you are not familiar with what is "mixed content", here are some places to learn more about it: