Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...A potentially dangerous Request.Form value was detected from the clientA potentially dangerous Request.Form value was detected from the client
Previous
 
Next
New Post
4/16/2012 1:34 AM
 
Hi all,

I am new to DNN. And I have been experiencing this error. I don't know what's causing it.
I think i really need some help on this one.  This error occur everytime I do changes on admin side. like adding page, edit the content of HTML module, or any other command/button from admin site. I cannot find what is causing the error.

Please help.
Thank you.

below is the error:

AssemblyVersion
: 5.5.1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL: /Default.aspx?tabid=42&error=A+potentially+dangerous+Request.Form+value+was+detected+from+the+client+(RibbonBar.ascx%24EditPage%24SkinLst%3d%22%3cUse+Default+Site+Sk...%22).&content=0
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20100101 Firefox/11.0
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 89181a1d-917c-4d92-a93a-d3c62c514b55
InnerException: A potentially dangerous Request.QueryString value was detected from the client (error="...$SkinLst="<Use Default Site Sk...").
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.HttpRequest.ValidateString
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: A potentially dangerous Request.QueryString value was detected from the client (error="...$SkinLst="<Use Default Site Sk..."). ---> System.Web.HttpRequestValidationException: A potentially dangerous Request.QueryString value was detected from the client (error="...$SkinLst="<Use Default Site Sk..."). at System.Web.HttpRequest.ValidateString(String value, String collectionKey, RequestValidationSource requestCollection) at System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, RequestValidationSource requestCollection) at System.Web.HttpRequest.get_QueryString() at DotNetNuke.HttpModules.UrlRewriteModule.RewriteUrl(HttpApplication app) at DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---
Source:
 
New Post
4/18/2012 9:32 PM
 
I have also tried to upgrade .Net framework to 4 and set validateRequest to false and it worked. It does not show the error anymore. The problem is that, I cannot let the validationRequest set to false since it will only set my site prone to SQL injections.

Do you have any other solutions?
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...A potentially dangerous Request.Form value was detected from the clientA potentially dangerous Request.Form value was detected from the client


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out