Skip to content
This repository was archived by the owner on Oct 24, 2020. It is now read-only.

Commit f60a496

Browse files
authored
Update Rulesets.md
Explain where rulesets are located.
1 parent 7801615 commit f60a496

1 file changed

Lines changed: 13 additions & 0 deletions

File tree

docs/en_US/rulesets.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ of rulesets that tell HTTPS Always which sites it should switch to HTTPS and how
66
If there is a site that offers HTTPS and is not handled by the extension, this guide
77
will explain how to add that site.
88

9+
Note: You may also consider using the companion addon [HTTPS Inquirer](https://github.com/g4jc/httpsinquirer) to generate rulesets automatically.
10+
911
#### [Rulesets](#rulesets)
1012

1113
A `ruleset` is an [XML](https://www.xml.com/pub/a/98/10/guide0.html?page=2) file
@@ -197,3 +199,14 @@ This generally breaks the site. Depending on their configuration and threat
197199
model, some users might however decide to enable these rulesets via a global
198200
option in HTTPS Always. To that effect, such rulesets are identified with
199201
the specific `platform="mixedcontent"` attribute to the ruleset element.
202+
203+
#### [Saving the Ruleset](#saving-the-ruleset)
204+
205+
Once you have created your ruleset it needs to be placed into the application profile directory under the `HTTPSAlwaysRulesets` folder.
206+
207+
e.g. On Windows:
208+
209+
`C:\Users\[your_username]\AppData\Roaming\Moonchild Productions\Pale Moon\Profiles\[your_profile].default\HTTPSAlwaysUserRules`
210+
211+
On GNU/Linux:
212+
`/home/user/.moonchild productions/pale moon/[your_profile].default/HTTPSAlwaysUserRules/`

0 commit comments

Comments
 (0)