]>
Commit | Line | Data |
---|---|---|
d4949327 NL |
1 | URI.Host\r |
2 | TYPE: string/null\r | |
3 | VERSION: 1.2.0\r | |
4 | DEFAULT: NULL\r | |
5 | --DESCRIPTION--\r | |
6 | \r | |
7 | <p>\r | |
8 | Defines the domain name of the server, so we can determine whether or\r | |
9 | an absolute URI is from your website or not. Not strictly necessary,\r | |
10 | as users should be using relative URIs to reference resources on your\r | |
11 | website. It will, however, let you use absolute URIs to link to\r | |
12 | subdomains of the domain you post here: i.e. example.com will allow\r | |
13 | sub.example.com. However, higher up domains will still be excluded:\r | |
14 | if you set %URI.Host to sub.example.com, example.com will be blocked.\r | |
15 | <strong>Note:</strong> This directive overrides %URI.Base because\r | |
16 | a given page may be on a sub-domain, but you wish HTML Purifier to be\r | |
17 | more relaxed and allow some of the parent domains too.\r | |
18 | </p>\r | |
19 | --# vim: et sw=4 sts=4\r |