230 Views
There is an issue with ASP.NET 4.0 and ASP.NET MVC 1 or 2 that causes the ValidateInput attribute, used to allow 'unsafe' content in requests, to no longer work. Here's a quick workaround.
0 comments
Join in on a hand-picked round up of the best .NET articles every day.
Curated by our Moderators and Voted up by our Community. Free.
There is an issue with ASP.NET 4.0 and ASP.NET MVC 1 or 2 that causes the ValidateInput attribute, used to allow 'unsafe' content in requests, to no longer work. Here's a quick workaround.