aboutsummaryrefslogtreecommitdiffhomepage
path: root/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/HTML.AllowedCommentsRegexp.txt
diff options
context:
space:
mode:
Diffstat (limited to 'inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/HTML.AllowedCommentsRegexp.txt')
-rw-r--r--inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/HTML.AllowedCommentsRegexp.txt15
1 files changed, 15 insertions, 0 deletions
diff --git a/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/HTML.AllowedCommentsRegexp.txt b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/HTML.AllowedCommentsRegexp.txt
new file mode 100644
index 00000000..b1e65beb
--- /dev/null
+++ b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/HTML.AllowedCommentsRegexp.txt
@@ -0,0 +1,15 @@
1HTML.AllowedCommentsRegexp
2TYPE: string/null
3VERSION: 4.4.0
4DEFAULT: NULL
5--DESCRIPTION--
6A regexp, which if it matches the body of a comment, indicates that
7it should be allowed. Trailing and leading spaces are removed prior
8to running this regular expression.
9<strong>Warning:</strong> Make sure you specify
10correct anchor metacharacters <code>^regex$</code>, otherwise you may accept
11comments that you did not mean to! In particular, the regex <code>/foo|bar/</code>
12is probably not sufficiently strict, since it also allows <code>foobar</code>.
13See also %HTML.AllowedComments (these directives are union'ed together,
14so a comment is considered valid if any directive deems it valid.)
15--# vim: et sw=4 sts=4