diff options
Diffstat (limited to 'inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.AllowHostnameUnderscore.txt')
-rw-r--r-- | inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.AllowHostnameUnderscore.txt | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.AllowHostnameUnderscore.txt b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.AllowHostnameUnderscore.txt new file mode 100644 index 00000000..405d36f1 --- /dev/null +++ b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.AllowHostnameUnderscore.txt | |||
@@ -0,0 +1,16 @@ | |||
1 | Core.AllowHostnameUnderscore | ||
2 | TYPE: bool | ||
3 | VERSION: 4.6.0 | ||
4 | DEFAULT: false | ||
5 | --DESCRIPTION-- | ||
6 | <p> | ||
7 | By RFC 1123, underscores are not permitted in host names. | ||
8 | (This is in contrast to the specification for DNS, RFC | ||
9 | 2181, which allows underscores.) | ||
10 | However, most browsers do the right thing when faced with | ||
11 | an underscore in the host name, and so some poorly written | ||
12 | websites are written with the expectation this should work. | ||
13 | Setting this parameter to true relaxes our allowed character | ||
14 | check so that underscores are permitted. | ||
15 | </p> | ||
16 | --# vim: et sw=4 sts=4 | ||