Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...DotNetNuke 5.4.4 Error when Creating Module - A potentially dangerous Request.QueryString value ..."DotNetNuke 5.4.4 Error when Creating Module - A potentially dangerous Request.QueryString value ..."
Previous
 
Next
New Post
7/28/2010 1:47 PM
 
Christopher


Joined: 6/27/2006
Posts: 198
Hello,

When attempting to create a module from the host section of a brand new DotNetNuke 5.4.4 site (from the Modules Definition Pages) I get the following error message. Any ideas?

Thank you for your time.


 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: <httpRuntime requestValidationMode="2.0" />. After setting this value, you can then disable request validation by setting validateRequest="false" in the Page directive or in the <pages> 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.

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

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace: 

[HttpRequestValidationException (0x80004005): A potentially dangerous Request.QueryString value was detected from the client (error="...$SkinLst="<Use Default Site Sk...").] System.Web.HttpRequest.ValidateString(String value, String collectionKey, RequestValidationSource requestCollection) +8730676 System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, RequestValidationSource requestCollection) +122 System.Web.HttpRequest.get_QueryString() +56 DotNetNuke.HttpModules.UrlRewriteModule.RewriteUrl(HttpApplication app) +375 DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +978 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +148 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

Regards,
Christopher Koeber
 
New Post
7/28/2010 7:20 PM
 
cathal connolly


cathal connolly's Avatar

www.cathal.co.uk
Joined: 4/9/2003
Posts: 9676
it appears you have request validation switched on - we disable this in DotNetNuke (we use our own filtering system which is more robust). Please check your web.config and ensure validateRequest is set to false i.e.

validateRequest="false"


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
7/28/2010 10:23 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
Also, if you are running the site install in an ASP.Net 4.0 application pool, you will need to add the following attribute to the system.web\httpRuntime section of your web.config file:

requestValidationMode="2.0"

DotNetNuke 5.4.x should make that change automatically when the site is installed in an existing ASP.Net 4.0 AppPool or when it detects that the pool has been changed to 4.0. However, if you had first opened the website in VS 2010 and allowed its changes to run under 4.0 I don't believe that DotNetNuke will be able to make the correct changes that it needs.

For more information, please see this MSDN white paper on breaking changes in ASP.Net 4.0:

http://www.asp.net/learn/whitepapers/...
Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
7/29/2010 8:52 PM
 
Christopher


Joined: 6/27/2006
Posts: 198
cathal connolly wrote:
it appears you have request validation switched on - we disable this in DotNetNuke (we use our own filtering system which is more robust). Please check your web.config and ensure validateRequest is set to false i.e.

validateRequest="false"


 
This has been already set in the web.config file. Thank you for the suggestion, though.

Regards,
Christopher Koeber
 
New Post
7/29/2010 8:53 PM
 
Christopher


Joined: 6/27/2006
Posts: 198
William Severance wrote:
Also, if you are running the site install in an ASP.Net 4.0 application pool, you will need to add the following attribute to the system.web\httpRuntime section of your web.config file:

requestValidationMode="2.0"

DotNetNuke 5.4.x should make that change automatically when the site is installed in an existing ASP.Net 4.0 AppPool or when it detects that the pool has been changed to 4.0. However, if you had first opened the website in VS 2010 and allowed its changes to run under 4.0 I don't believe that DotNetNuke will be able to make the correct changes that it needs.

For more information, please see this MSDN white paper on breaking changes in ASP.Net 4.0:

http://www.asp.net/learn/whitepapers/...

 Thanks! This was it.

As soon as I made that change everything worked!

Regards,
Christopher Koeber
 
 Page 1 of 1
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DotNetNuke 5.4.4 Error when Creating Module - A potentially dangerous Request.QueryString value ..."DotNetNuke 5.4.4 Error when Creating Module - A potentially dangerous Request.QueryString value ..."


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