«

I'm trying to stop .Net from validating data entered into a textbox. When I
enter < or > .Net returns an error:

potentially dangerous Request.Form value was detected from the client...

so a search on google indicates a couple of options:

1. Add validateRequest = "false" in the page directive. So I add it:

<%@ Page Language="vb" AutoEventWireup="false" Codebehind="addcode.aspx.vb"
Inherits="codelib.addcode" validateRequest="false"%>

but I get the error:

The 'validateRequest' attribute is not supported by the 'page' directive.

2. or add <pages validateRequest="false" /> in system.web of the web.config
file:

but when I do that I get the error:

Parser Error Message: Unrecognized attribute 'validateRequest'.

I guess I cannot use either of these with .Net 2002, which I have. Is there
any way around the first error caused by entering "malicious" code?

Tim,

This functionality was introduced in version 1.1 of the .NET framework. See
http://msdn.microsoft.com/library/en...protection.asp
for a way to add similar functionality to a version 1.0 application.

HTH,
Nicole



"Tim Zych" <tzych@earth_noworms_link_dotttt.net> wrote in message
news:...
> I'm trying to stop .Net from validating data entered into a textbox. When
> I
> enter < or > .Net returns an error:
>
> potentially dangerous Request.Form value was detected from the client...
>
> so a search on google indicates a couple of options:
>
> 1. Add validateRequest = "false" in the page directive. So I add it:
>
> <%@ Page Language="vb" AutoEventWireup="false"
> Codebehind="addcode.aspx.vb"
> Inherits="codelib.addcode" validateRequest="false"%>
>
> but I get the error:
>
> The 'validateRequest' attribute is not supported by the 'page' directive.
>
> 2. or add <pages validateRequest="false" /> in system.web of the
> web.config
> file:
>
> but when I do that I get the error:
>
> Parser Error Message: Unrecognized attribute 'validateRequest'.
>
> I guess I cannot use either of these with .Net 2002, which I have. Is
> there
> any way around the first error caused by entering "malicious" code?
>
>
>
>
>
>
>

Thanks for the article. It's over my head but it gives me some good insight.

"Nicole Calinoiu" <> wrote in message
news:#...
> Tim,
>
> This functionality was introduced in version 1.1 of the .NET framework.
See
>
http://msdn.microsoft.com/library/en...protection.asp
> for a way to add similar functionality to a version 1.0 application.
>
> HTH,
> Nicole
>
>
>
> "Tim Zych" <tzych@earth_noworms_link_dotttt.net> wrote in message
> news:...
> > I'm trying to stop .Net from validating data entered into a textbox.
When
> > I
> > enter < or > .Net returns an error:
> >
> > potentially dangerous Request.Form value was detected from the client...
> >
> > so a search on google indicates a couple of options:
> >
> > 1. Add validateRequest = "false" in the page directive. So I add it:
> >
> > <%@ Page Language="vb" AutoEventWireup="false"
> > Codebehind="addcode.aspx.vb"
> > Inherits="codelib.addcode" validateRequest="false"%>
> >
> > but I get the error:
> >
> > The 'validateRequest' attribute is not supported by the 'page'
directive.
> >
> > 2. or add <pages validateRequest="false" /> in system.web of the
> > web.config
> > file:
> >
> > but when I do that I get the error:
> >
> > Parser Error Message: Unrecognized attribute 'validateRequest'.
> >
> > I guess I cannot use either of these with .Net 2002, which I have. Is
> > there
> > any way around the first error caused by entering "malicious" code?
> >
> >
> >
> >
> >
> >
> >
>
>