Developer forum

Forum » Development » Webblog module comment to a post results in Application error (Dangerous Request)

Webblog module comment to a post results in Application error (Dangerous Request)


Reply

When making a comment to a blog post in the Webblog module the following

 

 

application error comes. Would be creat to beable to allow or disallow html / scripts etc. in comments in the module tab settings and not get application error of course :)

 

Server Error in '/' Application.


A potentially dangerous Request.Form value was detected from the client (txText="...est.dk

<a href="test">test<...").
Stack Trace:

[HttpRequestValidationException (0x80004005): A potentially dangerous Request.Form value was detected from the client (txText="...est.dk

<a href="test">test<...").]
   System.Web.HttpRequest.ValidateString(String s, String valueName, String collectionName) +8721914
   System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, String collectionName) +111
   System.Web.HttpRequest.get_Form() +129
   System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) +114
   System.Web.UI.Page.DeterminePostBackMode() +63
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6785
   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +242
   System.Web.UI.Page.ProcessRequest() +80
   System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21
   System.Web.UI.Page.ProcessRequest(HttpContext context) +49
   ASP.default_aspx.ProcessRequest(HttpContext context) in c:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\0cdcc88e\da874783\App_Web_iuz9bzuz.0.cs:0
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +181
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75
 

 

 


Replies

 
Reply

You probably haven't applied validaterequest="false" to the page directive of your Default.aspx.

 

You must be logged in to post in the forum