A potentially dangerous Request.Form value was detected from the client [modified]
-
Hi guys, Please forgive me, if it is a question frequent asked. As you know, when we tried to submit a asp.net page with characters something like '<test>' filled in, and we would get an error as the subject. How can the exception "A potentially dangerous Request.Form value was detected from the client" be handled without setting the validateRequest to false in the page directive or in the web.config file? because I just want to void this ASP.NET feature for only a single textbox, Any suggestions? Thanks, Ming.
modified on Wednesday, April 2, 2008 10:28 AM
-
Hi guys, Please forgive me, if it is a question frequent asked. As you know, when we tried to submit a asp.net page with characters something like '<test>' filled in, and we would get an error as the subject. How can the exception "A potentially dangerous Request.Form value was detected from the client" be handled without setting the validateRequest to false in the page directive or in the web.config file? because I just want to void this ASP.NET feature for only a single textbox, Any suggestions? Thanks, Ming.
modified on Wednesday, April 2, 2008 10:28 AM
Set
ValidateRequest=falseon the page.All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions
-
Set
ValidateRequest=falseon the page.All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions
Hi N a v a n e e t h, Thanks for your solution, but I think you don't understand what I am asking, you are alright, that is my fault, I didn't hightlight the key words. The key word is without setting the validateRequest to false in the page directive or in the web.config file? Cheers, Ming
-
Hi N a v a n e e t h, Thanks for your solution, but I think you don't understand what I am asking, you are alright, that is my fault, I didn't hightlight the key words. The key word is without setting the validateRequest to false in the page directive or in the web.config file? Cheers, Ming
Bluebamboo wrote:
The key word is without setting the validateRequest to false in the page directive or in the web.config file?
Ahh, I didn't noticed that :doh: . I don't think there is other way to do this. BTW, what is the problem for turning it off in page level or web.config ?
All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions
-
Bluebamboo wrote:
The key word is without setting the validateRequest to false in the page directive or in the web.config file?
Ahh, I didn't noticed that :doh: . I don't think there is other way to do this. BTW, what is the problem for turning it off in page level or web.config ?
All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions
because the basic requirement is that I provide a online html editor (implemented by using textbox) which allows user types in html markup , and submit to database. and also I have other textboxes on the same page which do need the asp.net pagevalidate feature, is any solution? any suggestion would be appricated! Cheers, Ming