I removed all the instances of Server.HtmlEncode, and then got complaints that the system was crashing out with the error: "A potentially dangerous Request.Form value was detected from the client ..."
How to achieve a happy medium? On Mar 8, 2:34 pm, stapes <[email protected]> wrote: > Hi > > I have inherited a buggy database that allows new users to register > from all over the world. Trouble is, many of their names are being > mangled by the Server.HtmlEncode command, which I assume is used to > prevent SQL Injection frauds and the like. > Is there any way I can get it to provide said protection but not > mangle foreign words with accents etc. -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
