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
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0A potentially dangerous Request.Cookies value was detected from the client (DNNPersonalization="<proA potentially dangerous Request.Cookies value was detected from the client (DNNPersonalization="
Previous
 
Next
New Post
7/24/2009 7:04 AM
 
Praveen prakash

Joined: 1/11/2008
Posts: 5

  Hi

I have hosted DNN site and My site(other than DNN)  on same server 

I am getting error 

A potentially dangerous Request.Cookies value was detected from the client (DNNPersonalization="<profile><item key="...").

 

Error Details:

A potentially dangerous Request.Cookies value was detected from the client (DNNPersonalization="<profile><item key="...").

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. You can 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. 

Exception Details: System.Web.HttpRequestValidationException: A potentially dangerous Request.Cookies value was detected from the client (DNNPersonalization="<profile><item key="...").

 

 

 

Because I have set validateRequest=true in my web.config file of my site I can't set validateRequest=false  due to CSS attacks.

Please guide me how I can avoid to DNN cookies to interfere my website.Its urgent!

Thanks

Thanks Praveen Prakash
 
New Post
7/24/2009 2:32 PM
 
Mitchel Sellers


Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

www.mitchelsellers.com
Joined: 1/24/2007
Posts: 7846

The way that DNN stores information in cookies I beileve will always cause problems with that feature enabled, therefore, I would not believe that this will be an easy task.

However, DNN validates input items, therefore this should not be a risk.  (I know of many DNN sites that have passed strict government security audits with the default configuration.)

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
7/27/2009 12:40 AM
 
Praveen prakash

Joined: 1/11/2008
Posts: 5
Dear Mitch, thank you for the prompt and detailed reply. Much appreciated!
Thanks Praveen Prakash
 
New Post
8/23/2010 3:58 PM
 
KNguyen


Joined: 5/28/2010
Posts: 25
Hi Chris, So how do I get rid of this error? I deleted cookies and try not to use it from my DNN website anymore but the error is still coming up from another non-dnn website. Is my machine basically damaged from this point on? I've also tried setting in web.config but it doesn't help. Thanks.
 
New Post
10/7/2010 2:56 AM
 
Joost van de Ven


Joined: 5/20/2010
Posts: 239
I have the same problem as KN huyen above, so an answer to his question would be much appreciated. I deleted all cookies and the error mentioned is still coming up from other non-dnn websites. It only appears in IE, not in Firefox. What can I do?!
 
 Page 1 of 1
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0A potentially dangerous Request.Cookies value was detected from the client (DNNPersonalization="<proA potentially dangerous Request.Cookies value was detected from the client (DNNPersonalization="


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