Portal Engine Questions on portal engine and web parts.
Version 5.x > Portal Engine > dangerous Request.Path value View modes: 
User avatar
Member
Member
francis.harvey-irisco - 11/3/2010 3:31:49 PM
   
dangerous Request.Path value
I get an exception from a page in my site

Here's the error:
A potentially dangerous Request.Path value was detected from the client (:). 
Stack Trace:
at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

i don't know why this happen, some internet search lead me to ValidateRequest property, already set to false.

Why this happen and how avoid it?

Thanks
Francis Harvey

User avatar
Kentico Consulting
Kentico Consulting
kentico_mirekr - 11/4/2010 8:00:09 AM
   
RE:dangerous Request.Path value
Hi,

Could you please let me know where exactly are you getting such exception (somewhere in CMS Desk/Site Manager interface or on your live site)?

Which version of KenticoCMS are you using (incl. hotfixes)?

Are you sure that there is following in your web.config file?
<pages validateRequest="false">
Is your web site accessible from the internet so we can see this behavior?

What are the steps to reproduce this issue?

Best regards,
Miroslav Remias.

User avatar
Member
Member
francis.harvey-irisco - 11/4/2010 9:16:52 AM
   
RE:dangerous Request.Path value
Hi Miroslav,

The version of KenticoCMS is 5.5 Build: 5.5.3789

Exception happens on the live site and i don't know how to reproduce the problem.

I only see these exceptions in the log.

The web.config has ValidateRequest = false property set

Can you provide me some testing step or anythings to reproduce the issue ?

Thanks
Francis Harvey

User avatar
Kentico Consulting
Kentico Consulting
kentico_mirekr - 11/16/2010 5:39:29 AM
   
RE:dangerous Request.Path value
Hi,

Well, we need to know under what kind of circumstances does this happen on your live site. If you are not able to reproduce this issue, then it could be very tricky to truck cause of this issue and I do not have any hints for you how to reproduce such issue on your live site. Isn’t there some more detail exception in your Kentico CMS event log which could lead us to specific page that fires such exception?

You are using Kentico CMS 5.5.3789 (build number) = 5.5.0 (hotfix number).

Could you please try to apply latest hotfix package?

http://devnet.kentico.com/Bugtracker/Hotfixes.aspx

Best regards,
Miroslav Remias.

User avatar
Certified Developer 8
Certified Developer 8
manoj-pulldigital - 11/30/2012 4:31:22 AM
   
RE:dangerous Request.Path value
Hi,

We seem to be getting this error in version 7 as an exception do you know why and what we can do to stop it, clogs up the event log?
EventDescription: Message: A potentially dangerous Request.Path value was detected from the client (?). 
Stack Trace:
at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)

Regards
Manoj

User avatar
Kentico Customer Success
Kentico Customer Success
kentico_martind2 - 12/2/2012 5:27:36 AM
   
RE:dangerous Request.Path value
Hi Manoj,

Have you tried to apply the latest hotfix? Were you upgrading from previous version?

In the future create a new thread under appropriate version forum please. Thank you.

Best regards,
Martin Danko

User avatar
Certified Developer 8
Certified Developer 8
manoj-pulldigital - 12/3/2012 3:20:14 AM
   
RE:dangerous Request.Path value
Yes, we have all the hot fixes up to:
7.0.8 got support telling me this is .Net related however there is not mention of a fix/ solution which we require.

Regads
Manoj

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 12/9/2012 1:43:24 AM
   
RE:dangerous Request.Path value
Hi,

Yes, it is basically a .Net thing, but you need to configure the application as well. Have you tried Google that error and tried the suggestion from the results? For example:

Stacoverflow suggestion 1
Stackoverflow no. 2 (and there are more similar questions with basically the same suggestions)
http://www.cryer.co.uk/brian/mswinswdev/ms_vbnet_server_error_potentially_dangerous.htm

Best regards,
Juraj Ondrus