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.QueryString value was detected...A potentially dangerous Request.QueryString value was detected...
Previous
 
Next
New Post
8/13/2010 2:44 PM
 
I get the following error in the documents module when I try to edit the exisitng information in the header field under the advanced setting of the module:

Server Error in '/' Application.

A potentially dangerous Request.QueryString value was detected from the client (error="...xtHeader="<font size="2" font ...").

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="...xtHeader="<font size="2" font ...").

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="...xtHeader="<font size="2" font ...").] 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 


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1


Since this site is on a server running the .NET 4.0 framework... would the validation mode be set incorrectly? requestValidationMode="2.0"? When I was having error with the linking of the files I hade to set the "integratedMode,runtimeversionv2.0" to "integratedMode,runtimeversionv4.0"

Any thoughts would be greatly appreciated.
 
New Post
8/13/2010 2:54 PM
 
I have found some information on this here:

http://weblogs.asp.net/anasghanem/arc...

and here:

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

However... when I add the line of code:

<httpRuntime requestValidationMode="2.0" />

to the web.config file I get a 500 error and the site does not come up... I also made sure that the (pages validateRequest="false") was set correctly... no luck... this is obvisouly a .NET 4.0 issues, how is this fixed? Thanks for any input.
 
New Post
8/13/2010 3:19 PM
 
I found that I had to add:

  <httpRuntime requestValidationMode="2.0" />

under the:

<system.web>
 
section... all is fixed... hope this helps others.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...A potentially dangerous Request.QueryString value was detected...A potentially dangerous Request.QueryString value was detected...


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