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

See more:

ASP.NET2

Dear Professionals,

We are using an ASP.net 2.0 Web Service in which there are some SOAP function calls and these remote functions return html strings which contain '>', '<' characters and many other special characters.

The Web service has been extensively used for many years now and only lately we get the "A potentially dangerous Request.Form value was detected from the client" exception.

We have googled and figured out the reason and also the proposed solutions that we need to put the validdateRequest='false' inside the Web.config, or include this in the @Page directive.

We tried the Web.config solution and it never worked out for us. As for the @Page directive, since this is an .asmx file we are not sure where to include this.


Please Help us with a solution.

Thanks in Advance.