Skip to content

Commit 4078246

Browse files
J0WIJ0WI
committed
Merge pull request EFForg#4131 from phibo23/letterboxd
new ruleset for letterboxd
2 parents 461e991 + 8f2e6dd commit 4078246

File tree

2 files changed

+34
-0
lines changed

2 files changed

+34
-0
lines changed

‎.gitignore‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ chromium.pem
33
dummy-chromium.pem
44
pkg/
55
src/chrome/content/rules/default.rulesets
6+
src/chrome/content/rulesets.json
67
src/defaults/rulesets.sqlite
78
*.swp
89
tokenkeys.py*

‎src/chrome/content/rules/Letterboxd.com.xml‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
<ruleset name="Letterboxd.com">
2+
<target host="letterboxd.com" />
3+
<target host="www.letterboxd.com" />
4+
5+
<!--
6+
the following subdomains don't support https yet but are listed here for reference
7+
-->
8+
9+
<!-- <target host="news.letterboxd.com" /> -->
10+
<!-- <target host="embed.letterboxd.com" /> -->
11+
<!-- <target host="feedback.letterboxd.com" /> -->
12+
13+
<!--
14+
there is also ltrbxd.com which appears to be mainly used for a cdn.
15+
However not all subdomains work correctly with https. For example,
16+
every file on a.ltrbxd.com is also available on skyfall.a.ltrbxd.com,
17+
oblivion.a.ltrbxd.com etc. These servers can be accessed with https
18+
but browsers will display errors/warnings because there is only a
19+
wildcard certificate for *.ltrbxd.com and not one for each of the subdomains.
20+
-->
21+
22+
<target host="a.ltrbxd.com" />
23+
<!-- <target host="*.a.ltrbxd.com" /> -->
24+
<target host="s1.ltrbxd.com" />
25+
<!-- <target host="*.s1.ltrbxd.com" /> -->
26+
<target host="s2.ltrbxd.com" />
27+
<!-- <target host="*.s2.ltrbxd.com" /> -->
28+
29+
<test url="http://letterboxd.com/" />
30+
<test url="http://www.letterboxd.com/" />
31+
32+
<rule from="^http:" to="https:" />
33+
</ruleset>

0 commit comments

Comments
 (0)