更新时间:2022-10-15 14:14:25
我觉得问题是,JavaScript不理解分组.NET的正前pression语法。
当您设置 EnableClientScript
到真
在 RegularEx pressionValidator
ASP.NET重新创建你的正常EX pression在JavaScript中你控制启用客户端验证。在这种情况下,JavaScript不支持语法命名组(小于?T> ...)
和非捕获组(? :...)
。虽然这些功能都支持.NET JavaScript是疲于应付他们。
从 RegularEx pressionValidator管制(一般参考)在MSDN上:
在客户端,JScript正 EX pression语法。在 服务器,正则表达式语法。因为 JScript正EX pression语法是 正则表达式语法的子集,它是 建议您使用的JScript 以常规EX pression语法 收率上相同的结果均 客户端和服务器。
有两种方法可以解决此:
EnableClientScript
到假
。(...)
语法应该在JavaScript和.NET正常工作。这样,你会使用序号引用访问捕获的值( $ 1
, $ 2
等)。像> [^<] *
应该发挥作用的。请参见 MSDN上的分组构造。
我想指出几个其他的问题:
> [^&所述;] *
这将是更简单和工作方式完全相同。它不会捕获任何值的原始字符串,但由于您使用的是一个ASP.NET验证控件在这不应该的问题。 RegularEx pressionValidator
只会工作,如果匹配成功的方式。在你的情况,您的验证将通过,如果你的文本框包含类似>等等
。我想你想要的其他方式使用。> [^<] *
,常规的前pression仍然没有工作,我是怎么想的你想让它。该验证控件尝试匹配在文本框中的所有文本。所以,如果我输入>等等
在文本框中,它将匹配,但< B>等等< / B>
不会因为常规的前pression表示,该字符串必须以>
。我会建议尝试像 *> *。[^<] *
允许前文>
。I have the following regular expression validator to detect whether an input string contains HTML/script tags and if so cause a vaidation error:
<asp:TextBox ID="txt" runat="server" />
<asp:RegularExpressionValidator
ControlToValidate="txt"
runat="server"
ID="regexVal"
EnableClientScript="true" Display="Dynamic"
ErrorMessage="Invalid Content"
Text="!"
ValidationExpression=">(?:(?<t>[^<]*))" />
When I run the page hosting this markup I get a scipt error with the message "Syntax Error in Regular Expression". However when I take the same regex and run it using Regex class from System.Text.RegularExpressions everything works fine: Like so:
Regex r = new Regex(">(?:(?<t>[^<]*))");
r.IsMatch(@"<b>This should cause a validation error</b>");
r.IsMatch("this is fine");
What am I missing
UPDATE: The error seems to be happening in the following js function in WebResource.axd:
function RegularExpressionValidatorEvaluateIsValid(val) {
var value = ValidatorGetValue(val.controltovalidate);
if (ValidatorTrim(value).length == 0)
return true;
var rx = new RegExp(val.validationexpression); //this is the line causing the error
var matches = rx.exec(value);
return (matches != null && value == matches[0]);
}
I think the problem is that JavaScript does not understand .NET's regular expression syntax for grouping.
When you set EnableClientScript
to true
on the RegularExpressionValidator
ASP.NET re-creates your regular expression in JavaScript to enable client-side validation on you controls. In this case, JavaScript doesn't support the syntax for named groups (?<t>...)
and non-capturing groups (?:...)
. While these features work in .NET JavaScript is struggling with them.
From RegularExpressionValidator Control (General Reference) on MSDN :
On the client, JScript regular expression syntax is used. On the server, Regex syntax is used. Because JScript regular expression syntax is a subset of Regex syntax, it is recommended that you use JScript regular expression syntax in order to yield the same results on both the client and the server.
There are two ways you can correct this:
EnableClientScript
to false
.(...)
syntax should work correctly in both JavaScript and .NET. You would then use ordinal number references to access captured values ($1
, $2
, etc.). Something like >[^<]*
should work as intended. See Grouping Constructs on MSDN.I'd like to point out a couple of other issues:
>[^<]*
which will be simpler and work exactly the same way. It won't capture any values in the original string, but since you're using it in an ASP.NET validation control this shouldn't matter.RegularExpressionValidator
will only work if the match is successful. In your case, your validation will pass if your textbox contains something like >blah
. I think you want it to work the other way around.>[^<]*
, the regular expression will still not work how I think you intend it to. The validation control tries to match all text in the textbox. So if I enter >blah
in the textbox, it will match, but <b>blah</b>
won't because the regular expression says that the string must start with a >
. I would suggest trying something like .*>.*[^<]*
to allow text before the >
.