Rank: Member
Joined: 1/15/2008(UTC) Posts: 58
|
Just recently, Our Search function has stopped working entirely. Both Advanced Search and Key Word Search Box no longer return any results.
Also noticing a new recurring Error message in the Event Log:
Error: System.Web A potentially dangerous Request.Form value was detected from the client (ctl00$MainContentHolder$ContentColumnControl3$ctl00$KeywordField="...t lesbian <a href="http://www....").[ at System.Web.HttpRequest.ValidateString(String s, String valueName, String collectionName) 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 ASP.bvmodules_producttemplates_johnprodtemplate_product_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) ]
Any Ideas ?
Hosting with Applied-I VS-1 Plan BVC 5.3.1
|
|
|
|
Rank: Member
Joined: 11/5/2003(UTC) Posts: 2,136
Was thanked: 1 time(s) in 1 post(s)
|
The error message is not an error. The software stopped some sort of injection attack and recorded that fact.
I don't know why search stopped working, but it is not related to the message. |
|
|
|
|
Rank: Member
Joined: 8/1/2007(UTC) Posts: 310
|
You get this error when script tags or html tags are part of your search. This is standard ASP.Net security measure to avoid script injection attacks. You can disable this for a specific page (in this case search.aspx) by adding the RequestValidation="False" tag to the page directive on your aspx file (the first line). This is a fix. But you should look into why thats happening in the first place. Did you change any search related stuff? |
Thanks, Satya support @ bayquel.net Work: +1 803 883 3226 |
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.