From 9de100f2f422ce4318d70389c723c36e456c442c Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Thu, 23 Oct 2014 19:43:12 -0400 Subject: [PATCH 1/2] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7f51d5b..c748629 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # µMatrix for Chromium -[Under development: usable, but persistence schema not finalized, will certainly change] +[Under development: usable, but not stable, many things broken because in the midst of general refactoring] Forked from [HTTP Switchboard](https://github.com/gorhill/httpswitchboard). From 6b8f64281d3f5b222da312e3d52916192ca35d79 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Thu, 23 Oct 2014 19:47:04 -0400 Subject: [PATCH 2/2] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index c748629..375c72e 100644 --- a/README.md +++ b/README.md @@ -13,6 +13,7 @@ Differences with HTTP Switchboard: - Z is the source hostname axis (aka "scope"), from narrower scopes to global scope - X is the request type axis: `*`, `cookie`, `css`, etc. - Y is the destination hostname axis (`www.example.com`, `example.com`, `com`, `*`) + - Thus, **every** request is evaluated starting from the scope as per request's hostname, down to global scope if no explicit rule is found on the way down. - Switching scopes in matrix popup does not create/delete scopes, this just allows a user to modify rules in a specific scope - Rules in narrower scope(s) still exist and are enforced even if you have the global scope selected - Settings which no longer exist: