|
1 | 1 | <!-- |
| 2 | + As of August 2014, CATO seems to reject all connections to :443 |
| 3 | +
|
2 | 4 | CDN bucket: |
3 | 5 |
|
4 | 6 | - wac.0873.edgecastcdn.net/800873 |
|
15 | 17 | --> |
16 | 18 | <ruleset name="Cato Institute (partial)"> |
17 | 19 |
|
18 | | - <target host="cato.com" /> |
19 | | - <target host="*.cato.com" /> |
| 20 | + <target host="secure.cato.org" /> |
20 | 21 |
|
21 | 22 |
|
22 | 23 | <!-- NB: This coverage is incomplete. |
|
25 | 26 |
|
26 | 27 | It seems that all pages at least two directories deep can be fetched via https |
27 | 28 | --> |
28 | | - <rule from="^https?://(?:www\.)?cato\.org/([^/]+/[^/]+)/" |
29 | | - to="https://www.cato.org/$1/" /> |
| 29 | + <!-- <rule from="^https?://(?:www\.)?cato\.org/([^/]+/[^/]+)/" |
| 30 | + to="https://www.cato.org/$1/" /> --> |
30 | 31 |
|
31 | 32 | <!-- the above rewrite makes the server print https links that point to pages which |
32 | 33 | don't support https. We need to rewrite these links back to http before dealing |
33 | 34 | with non-page paths below, since the paths below are matched here too. |
34 | 35 | The paths that don't work comprise anything which isn't at least two |
35 | 36 | directory levels deep. --> |
36 | | - <rule from="^https://www\.cato\.org/([^/]+/?(?:[^/]+/?)?)?$" |
37 | | - to="http://www.cato.org/$1" downgrade="1" /> |
| 37 | + <!-- <rule from="^https://www\.cato\.org/([^/]+/?(?:[^/]+/?)?)?$" |
| 38 | + to="http://www.cato.org/$1" downgrade="1" /> --> |
38 | 39 |
|
39 | 40 | <!-- Account-related pages and non-page paths that support https. Not all do so. --> |
40 | | - <rule from="^https?://(?:www\.)?cato\.org/(images/|store/(?:sites/|user/(?:password|register)))" |
41 | | - to="https://www.cato.org/$1" /> |
| 41 | + <!-- <rule from="^https?://(?:www\.)?cato\.org/(images/|store/(?:sites/|user/(?:password|register)))" |
| 42 | + to="https://www.cato.org/$1" /> --> |
42 | 43 |
|
43 | 44 | <rule from="^http://secure\.cato\.org/" |
44 | 45 | to="https://secure.cato.org/" /> |
|
0 commit comments