在此示例中,我正在使用Sitefinity 5.1和RadGrid。Sitefinity从客户端(?)检测到潜在危险的Request.Path值
我一直在排除故障今晨我方开发服务器上的一个网页,我已经证实,它具有不同的行为与样式(模板)在页面上比准系统页面(没有造型,没有脚本等)上:
- 的页面不在Chrome工作,但确实在IE和Firefox
- 一个最基本的网页(无模板,头,或其他任何东西)上的页面工作在IE,Firefox和Chrome
使用的代码:
Response.Redirect(String.Format("~/services/separation-by-code/managesbyc?id={0}", DateTime.Now.Ticks.ToString()));
我在使用ticks刷新页面之前到达那里。
下面是一些结果:
火狐: seabass.ptagis.org/services/separation-by-code/managesbyc?id=634854696522350585 - >工作
铬的裸机Sitefinity页: seabass.ptagis.org/services/separation-by-code/managesbyc?id=634854701574768045 - >的风格页面(CSS,Scritps等)上工作
铬: seabass.ptagis.org/services/ %2fservices%2fseparation-by-code%2fmanagesbyc%3fid%3d634854699444302751 - > nope
我得到下面附加的服务器错误。
我完成了设置web.config httprequests = 2.0和page validations = false的所有步骤。这没有帮助。
任何帮助表示赞赏。
Server Error in '/' Application. A potentially dangerous Request.Path value was detected from the client (?). Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: A potentially dangerous Request.Path value was detected from the client (?). 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: [HttpException (0x80004005): A potentially dangerous Request.Path value was detected from the client (?).]
System.Web.HttpRequest.ValidateInputIfRequiredByConfig() +11494475
System.Web.PipelineStepManager.ValidateHelper(HttpContext context) +184 Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272
你也可以在httpRuntime中使用requestValidationMode =“2.0” –