at System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, String collectionName)
at System.Web.HttpRequest.get_Form()
at System.Web.HttpRequest.get_HasForm()
at System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull)
at System.Web.UI.Page.DeterminePostBackMode()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean completedSynchronously) |
 |
|
Solution:
|
ASP.NET performs request validation against query-string and form variables as well as cookie values. By default, if the current Request contains HTML-encoded elements (such as <a>, <input> tags) or certain HTML characters (such as — for an em dash), the ASP.NET page framework raises an error.
For instance, you have a text field in the form, and users typed some text containing html tag such as <a href="abc.com">.
If you want your application to accept some HTML tags, you should encode the HTML at the client before it is submitted to the server. For instance, <a> for <a> tag.
|
 |
|
About the contributor of this solution to the exception:
Aspexception.com is dedicated to the solutions for exceptions in .NET technologies
|
|