Comments on: ASP.NET potentially dangerous Request.Form value

By: codeprostitute

codeprostitute — Tue, 03 Jul 2007 13:37:45 +0000

FYI – Should you choose to disable this, it is a good idea to use Server.HtmlEncode on the input value if the input will ever be displayed.

By: MrEyes

MrEyes — Tue, 10 Oct 2006 11:24:39 +0000

Adding this to the web.config in the manner described above will disable validation for the entire site. This may or may not be desirable.

You can disable at a page level by adding the following:

validateRequest=“false”

To the

directive at the top of your page

By: the tinman

the tinman — Tue, 11 Apr 2006 21:48:59 +0000

Well, if MSFT provided a way to CONFIGURE this option, such that your code could still work, while the filter searched for OTHER dangerous requests, THAT would be the solution. Alas…

By: bk

bk — Mon, 13 Feb 2006 19:13:30 +0000

what a good idea! For once, MSFT warns you about a security issue and the solution is to disable the warning.