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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...[5.4.0] A potentially dangerous Request.QueryString[5.4.0] A potentially dangerous Request.QueryString
Previous
 
Next
New Post
4/20/2010 12:37 PM
 

I installed fresh DNN 5.4.0 on .NET 4.0 (IIS 7.5) and after login when I click any javascript link I get this error, is this wrong setting on my side, or bug in new release?

A potentially dangerous Request.QueryString value was detected from the client (error="...$SkinLst="<Use Default Site Sk...").

 Description: Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted. This value may indicate an attempt to compromise the security of your application, such as a cross-site scripting attack. To allow pages to override application request validation settings, set the requestValidationMode attribute in the httpRuntime configuration section to requestValidationMode="2.0". Example: . After setting this value, you can then disable request validation by setting validateRequest="false" in the Page directive or in the configuration section. However, it is strongly recommended that your application explicitly check all inputs in this case. For more information, see http://go.microsoft.com/fwlink/?LinkId=153133. 

 
New Post
4/20/2010 1:31 PM
 

Well I'll give shot to MS's advice, so I added requestValidationMode="2.0" and its working, probably something to do with changes in .NET 4.0. Wasn't sure if I should do it, as seemed illogical to throw this error when validateRequest on pages is already off and VS2010 deemed it not necessary when upgrading :).

 
New Post
4/20/2010 1:50 PM
 
we automate the adding of this attribute when you deploy a site to a .net 4.0 application pool, however we can't do this when you open up a site in vs.net 2010, hence the issue.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
4/28/2010 6:41 PM
 

I'm completely new to DNN and indeed a novice.  I too am getting this error and despite all efforts, can't fix it.  Where should I add the expression as described - my fix isn't working and the only difference is I have IIS 6.0

Chris

 
New Post
4/28/2010 8:09 PM
 
chris, did you upgrade to .Net 4.0 or are you experiencing a different issue? please post detailed error message.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...[5.4.0] A potentially dangerous Request.QueryString[5.4.0] A potentially dangerous Request.QueryString


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