产品使用及交流论坛

注册

 

QQ登录

只需一步,快速开始

发新话题 回复该主题

Server Error in '/' Application问题 [复制链接]

1#
之前没有这个问题,使用好好的,可是今天怎么操作,网站参数设置-提交后才提示这个问题。

A potentially dangerous Request.Form value was detected from the client (wz_top="<script src="/e/js/T..."). 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.Form value was detected from the client (wz_top="<script src="/e/js/T...").

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[HttpRequestValidationException (0x80004005): A potentially dangerous Request.Form value was detected from the client (wz_top="<script src="/e/js/T...").]   System.Web.HttpRequest.ValidateString(String value, String collectionKey, RequestValidationSource requestCollection) +8939908   System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, RequestValidationSource requestCollection) +122   System.Web.HttpRequest.get_Form() +150   System.Web.HttpRequest.get_HasForm() +9119279   System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) +97   System.Web.UI.Page.DeterminePostBackMode() +69   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +8431   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +253   System.Web.UI.Page.ProcessRequest() +78   System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21   System.Web.UI.Page.ProcessRequest(HttpContext context) +49   ASP.e_master_set_1_aspx.ProcessRequest(HttpContext context) +4   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +100   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1031
我已经按论坛中的相关帮助及大家提的和操作的做了,还是老样子。大家帮我看一下,是不是我升级asp.net过高还是什么问题。其他操作正常就是网站基础设置这里无法保存。
分享 转发
TOP
2#
TOP
3#

<httpRuntime maxRequestLength="10240" executionTimeout="60"  />
修改为
<httpRuntime maxRequestLength="10240" executionTimeout="60"  requestValidationMode="2.0"/>

改成这样的就OK了,不过之前好像也没有啊。升级后好像也没有发现,现在出现了,可能是我asp.net版过高的原因。谢谢!问题处理完结
TOP
发新话题 回复该主题