[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).
Forked from [HTTP Switchboard](https://github.com/gorhill/httpswitchboard).
@ -13,6 +13,7 @@ Differences with HTTP Switchboard:
- Z is the source hostname axis (aka "scope"), from narrower scopes to global scope
- Z is the source hostname axis (aka "scope"), from narrower scopes to global scope
- X is the request type axis: `*`, `cookie`, `css`, etc.
- X is the request type axis: `*`, `cookie`, `css`, etc.
- Y is the destination hostname axis (`www.example.com`, `example.com`, `com`, `*`)
- 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
- 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
- Rules in narrower scope(s) still exist and are enforced even if you have the global scope selected
gorhill
10 years ago