blocks|key|4714893|text|我发现问题出在Error.aspx上。仍然找不到导致问题的error.aspx中的实际错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4714894|将页面更改为静态html文件解决了此问题。|4714895|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I found that the problem was in Error.aspx. Still can't find what was the actual error in error.aspx that causes the problem.

Changing the page to a static html file solved the problem.

blocks|key|4715078|text|对于试图在MVC应用程序中执行此操作的任何人来说，ResponseRewrite在幕后使用Server.Transfer，这一点很重要。因此，defaultRedirect必须与文件系统上的合法文件相对应。显然，错误与MVC路由不兼容，因此，如果您的错误页面由控制器操作提供，Server.Transfer将查找/+Server.Transfer+/任何内容，而不是在文件系统中找到它，并返回一个通用的404错误页面！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4715079|entityMap^0|P|F|19|F|1Z|F|3U|F|4E|F|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|G|$]]

It is important to note for anyone trying to do this in an MVC application that <code>ResponseRewrite</code> uses <code>Server.Transfer</code> behind the scenes. Therefore, the <code>defaultRedirect</code> must correspond to a legitimate file on the file system. Apparently, <code>Server.Transfer</code> is not compatible with MVC routes, therefore, if your error page is served by a controller action, <code>Server.Transfer</code> is going to look for /Error/Whatever, not find it on the file system, and return a generic 404 error page!

blocks|key|652016|text|对我来说完美工作的唯一方法是关闭自定义错误，并通过web.config替换iis的错误页面。它将正确的状态代码与响应一起发送，并具有无需通过mvc的好处。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|652017|下面是代码|652018|652019|关闭自定义错误|ordered-list-item|652020|652021|652022|替换错误页|unordered-list-item|652023|652024|652025|请注意。如果url是指向文件的直接链接，则使用responsemode="file"|offset|length|style|CODE|652026|信息：http://tipila.com/tips/use-custom-error-pages-aspnet-mvc|652027|entityMap|0|LINK|mutability|MUTABLE|url|http://tipila.com/tips/use-custom-error-pages-aspnet-mvc^0|0|0|0|0|0|0|0|0|0|N|J|0|3|1K|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|17|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1A|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1D|8|@$Q|1E|R|1F|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1G|8|@]|9|@$Q|1H|R|1I|1|1J]]|A|$]]|$1|W|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

The only way that worked perfectly for me is to turn off custom errors and replace iis's error pages via web.config. It sends the correct status code with the response and has the benefit of not going through the mvc.

here's the code 



<ol>
<li>Turn off custom errors

<pre class="lang-xml prettyprint-override"><code>&lt;customErrors mode="Off" /&gt;
</code></pre></li>
<li>Replace error pages

<pre class="lang-xml prettyprint-override"><code>&lt;httpErrors errorMode="Custom" existingResponse="Replace"&gt;
 &lt;remove statusCode="404" subStatusCode="-1" /&gt;
 &lt;remove statusCode="500" subStatusCode="-1" /&gt;
 &lt;error statusCode="404" path="Error404.html" responseMode="File" /&gt;
 &lt;error statusCode="500" path="Error.html" responseMode="File" /&gt;
&lt;/httpErrors&gt;
</code></pre></li>
</ol>

Note. Use <code>responsemode="file"</code> if the url is a direct link to a file

info : <a href="http://tipila.com/tips/use-custom-error-pages-aspnet-mvc">http://tipila.com/tips/use-custom-error-pages-aspnet-mvc</a>

blocks|key|651878|text|实际情况是，IIS正在查看错误状态代码，并显示它自己的错误页面，而不是您的页面。要解决此问题，您需要在错误页的代码隐藏页中设置此设置，以防止IIS执行此操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|651879|Response.TrySkipIisCustomErrors+=+true;|code-block|syntax|javascript|651880|这只适用于IIS7或更高版本，对于早期版本的IIS，您需要尝试错误页面设置。|651881|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

What's happening is IIS is seing the error status code and presenting it's own error page instead of yours. To solve you need to set this in the code behind page of your error page to prevent IIS from doing this:

<pre><code>Response.TrySkipIisCustomErrors = true;
</code></pre>

This will only work in IIS7 or above, for earlier versions of IIS you'll need to play with the error page settings.

blocks|key|4715243|text|由于对Server.Transfer的依赖，ResponseRewrite的内部实现似乎与MVC不兼容。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4715244|对我来说，这似乎是一个明显的功能漏洞，所以我决定使用HTTP模块重新实现这个功能，这样它就可以在上工作了。下面的解决方案允许您通过重定向到任何有效的MVC路由(包括物理文件)来处理错误，就像您通常所做的那样。|BOLD|4715245|<customErrors+mode="RemoteOnly"+redirectMode="ResponseRewrite">
++++<error+statusCode="404"+redirect="404.aspx"+/>
++++<error+statusCode="500"+redirect="~/MVCErrorPage"+/>
</customErrors>|code-block|syntax|javascript|4715246|这已经在以下平台上进行了测试；|4715247|集成管道模式下的|4715248|MVC4+(IIS6+8)经典模式下的|unordered-list-item|4715249|MVC4+(VS开发服务器，卡西尼)经典模式下的|4715250|MVC4+(IIS6)|4715251|4715252|4715253|namespace+Foo.Bar.Modules+{

++++///+<summary>
++++///+Enables+support+for+CustomErrors+ResponseRewrite+mode+in+MVC.
++++///+</summary>
++++public+class+ErrorHandler+:+IHttpModule+{

++++++++private+HttpContext+HttpContext+{+get+{+return+HttpContext.Current;+}+}
++++++++private+CustomErrorsSection+CustomErrors+{+get;+set;+}

++++++++public+void+Init(HttpApplication+application)+{
++++++++++++System.Configuration.Configuration+configuration+=+WebConfigurationManager.OpenWebConfiguration("~");
++++++++++++CustomErrors+=+(CustomErrorsSection)configuration.GetSection("system.web/customErrors");

++++++++++++application.EndRequest+%2B=+Application_EndRequest;
++++++++}

++++++++protected+void+Application_EndRequest(object+sender,+EventArgs+e)+{

++++++++++++//+only+handle+rewrite+mode,+ignore+redirect+configuration+(if+it+ain't+broke+don't+re-implement+it)
++++++++++++if+(CustomErrors.RedirectMode+==+CustomErrorsRedirectMode.ResponseRewrite+&&+HttpContext.IsCustomErrorEnabled)+{

++++++++++++++++int+statusCode+=+HttpContext.Response.StatusCode;

++++++++++++++++//+if+this+request+has+thrown+an+exception+then+find+the+real+status+code
++++++++++++++++Exception+exception+=+HttpContext.Error;
++++++++++++++++if+(exception+!=+null)+{
++++++++++++++++++++//+set+default+error+status+code+for+application+exceptions
++++++++++++++++++++statusCode+=+(int)HttpStatusCode.InternalServerError;
++++++++++++++++}

++++++++++++++++HttpException+httpException+=+exception+as+HttpException;
++++++++++++++++if+(httpException+!=+null)+{
++++++++++++++++++++statusCode+=+httpException.GetHttpCode();
++++++++++++++++}

++++++++++++++++if+((HttpStatusCode)statusCode+!=+HttpStatusCode.OK)+{

++++++++++++++++++++Dictionary<int,+string>+errorPaths+=+new+Dictionary<int,+string>();

++++++++++++++++++++foreach+(CustomError+error+in+CustomErrors.Errors)+{
++++++++++++++++++++++++errorPaths.Add(error.StatusCode,+error.Redirect);
++++++++++++++++++++}

++++++++++++++++++++//+find+a+custom+error+path+for+this+status+code
++++++++++++++++++++if+(errorPaths.Keys.Contains(statusCode))+{
++++++++++++++++++++++++string+url+=+errorPaths[statusCode];

++++++++++++++++++++++++//+avoid+circular+redirects
++++++++++++++++++++++++if+(!HttpContext.Request.Url.AbsolutePath.Equals(VirtualPathUtility.ToAbsolute(url)))+{

++++++++++++++++++++++++++++HttpContext.Response.Clear();
++++++++++++++++++++++++++++HttpContext.Response.TrySkipIisCustomErrors+=+true;

++++++++++++++++++++++++++++HttpContext.Server.ClearError();

++++++++++++++++++++++++++++//+do+the+redirect+here
++++++++++++++++++++++++++++if+(HttpRuntime.UsingIntegratedPipeline)+{
++++++++++++++++++++++++++++++++HttpContext.Server.TransferRequest(url,+true);
++++++++++++++++++++++++++++}
++++++++++++++++++++++++++++else+{
++++++++++++++++++++++++++++++++HttpContext.RewritePath(url,+false);

++++++++++++++++++++++++++++++++IHttpHandler+httpHandler+=+new+MvcHttpHandler();
++++++++++++++++++++++++++++++++httpHandler.ProcessRequest(HttpContext);
++++++++++++++++++++++++++++}

++++++++++++++++++++++++++++//+return+the+original+status+code+to+the+client
++++++++++++++++++++++++++++//+(this+won't+work+in+integrated+pipleline+mode)
++++++++++++++++++++++++++++HttpContext.Response.StatusCode+=+statusCode;

++++++++++++++++++++++++}
++++++++++++++++++++}

++++++++++++++++}

++++++++++++}

++++++++}

++++++++public+void+Dispose()+{

++++++++}


++++}

}|4715254|使用|4715255|将其作为web.config中的最终HTTP模块|4715256|++<system.web>
++++<httpModules>
++++++<add+name="ErrorHandler"+type="Foo.Bar.Modules.ErrorHandler"+/>
++++</httpModules>
++</system.web>

++
++<system.webServer>
++++<modules>
++++++<add+name="ErrorHandler"+type="Foo.Bar.Modules.ErrorHandler"+/>
++++</modules>
++</system.webServer>|4715257|entityMap^0|3|F|M|F|0|17|5|0|0|0|0|0|0|0|0|0|0|0|2|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1F|8|@$9|1G|A|1H|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|1I|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|1J|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1K|8|@]|D|@]|E|$]]|$1|R|3|S|5|T|7|1L|8|@]|D|@]|E|$]]|$1|U|3|V|5|T|7|1M|8|@]|D|@]|E|$]]|$1|W|3|X|5|T|7|1N|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1P|8|@]|D|@]|E|$]]|$1|10|3|11|5|K|7|1Q|8|@]|D|@]|E|$L|M]]|$1|12|3|13|5|6|7|1R|8|@$9|1S|A|1T|B|H]]|D|@]|E|$]]|$1|14|3|15|5|6|7|1U|8|@]|D|@]|E|$]]|$1|16|3|17|5|K|7|1V|8|@]|D|@]|E|$L|M]]|$1|18|3|-4|5|6|7|1W|8|@]|D|@]|E|$]]]|19|$]]

Due to the reliance on <code>Server.Transfer</code> it seems that the internal implementation of <code>ResponseRewrite</code> isn't compatible with MVC.

This seems like a glaring functionality hole to me, so I decided to re-implement this feature using a HTTP module, so that it just works. The solution below allows you to handle errors by redirecting to any valid MVC route (including physical files) just as you would do normally.

<pre><code>&lt;customErrors mode="RemoteOnly" redirectMode="ResponseRewrite"&gt;
 &lt;error statusCode="404" redirect="404.aspx" /&gt;
 &lt;error statusCode="500" redirect="~/MVCErrorPage" /&gt;
&lt;/customErrors&gt;
</code></pre>

This has been tested on the following platforms;

<ul>
<li>MVC4 in Integrated Pipeline Mode (IIS Express 8)</li>
<li>MVC4 in Classic Mode (VS Development Server, Cassini)</li>
<li>MVC4 in Classic Mode (IIS6)</li>
</ul>

<hr>

<pre><code>namespace Foo.Bar.Modules {

 /// &lt;summary&gt;
 /// Enables support for CustomErrors ResponseRewrite mode in MVC.
 /// &lt;/summary&gt;
 public class ErrorHandler : IHttpModule {

 private HttpContext HttpContext { get { return HttpContext.Current; } }
 private CustomErrorsSection CustomErrors { get; set; }

 public void Init(HttpApplication application) {
 System.Configuration.Configuration configuration = WebConfigurationManager.OpenWebConfiguration("~");
 CustomErrors = (CustomErrorsSection)configuration.GetSection("system.web/customErrors");

 application.EndRequest += Application_EndRequest;
 }

 protected void Application_EndRequest(object sender, EventArgs e) {

 // only handle rewrite mode, ignore redirect configuration (if it ain't broke don't re-implement it)
 if (CustomErrors.RedirectMode == CustomErrorsRedirectMode.ResponseRewrite &amp;&amp; HttpContext.IsCustomErrorEnabled) {

 int statusCode = HttpContext.Response.StatusCode;

 // if this request has thrown an exception then find the real status code
 Exception exception = HttpContext.Error;
 if (exception != null) {
 // set default error status code for application exceptions
 statusCode = (int)HttpStatusCode.InternalServerError;
 }

 HttpException httpException = exception as HttpException;
 if (httpException != null) {
 statusCode = httpException.GetHttpCode();
 }

 if ((HttpStatusCode)statusCode != HttpStatusCode.OK) {

 Dictionary&lt;int, string&gt; errorPaths = new Dictionary&lt;int, string&gt;();

 foreach (CustomError error in CustomErrors.Errors) {
 errorPaths.Add(error.StatusCode, error.Redirect);
 }

 // find a custom error path for this status code
 if (errorPaths.Keys.Contains(statusCode)) {
 string url = errorPaths[statusCode];

 // avoid circular redirects
 if (!HttpContext.Request.Url.AbsolutePath.Equals(VirtualPathUtility.ToAbsolute(url))) {

 HttpContext.Response.Clear();
 HttpContext.Response.TrySkipIisCustomErrors = true;

 HttpContext.Server.ClearError();

 // do the redirect here
 if (HttpRuntime.UsingIntegratedPipeline) {
 HttpContext.Server.TransferRequest(url, true);
 }
 else {
 HttpContext.RewritePath(url, false);

 IHttpHandler httpHandler = new MvcHttpHandler();
 httpHandler.ProcessRequest(HttpContext);
 }

 // return the original status code to the client
 // (this won't work in integrated pipleline mode)
 HttpContext.Response.StatusCode = statusCode;

 }
 }

 }

 }

 }

 public void Dispose() {

 }


 }

}
</code></pre>

Usage

Include this as the final HTTP module in your web.config

<pre><code> &lt;system.web&gt;
 &lt;httpModules&gt;
 &lt;add name="ErrorHandler" type="Foo.Bar.Modules.ErrorHandler" /&gt;
 &lt;/httpModules&gt;
 &lt;/system.web&gt;

 &lt;!-- IIS7+ --&gt;
 &lt;system.webServer&gt;
 &lt;modules&gt;
 &lt;add name="ErrorHandler" type="Foo.Bar.Modules.ErrorHandler" /&gt;
 &lt;/modules&gt;
 &lt;/system.webServer&gt;
</code></pre>

blocks|key|4714925|text|我知道这个问题有点老了，但我想我应该指出，它不需要是一个静态文件才能正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4714926|我遇到了类似的事情，这只是在你的Error.aspx中找到错误的问题，在我们的例子中，这是因为正在使用的母版页依赖于一段会话数据，并且当ResponseRewrite被设置时，会话对我们的Error.aspx页面不可用。|4714927|我还没有弄清楚会话的不可用是由于我们特定的应用程序配置还是由于ASP.net的“设计”部分。|4714928|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I know this question is a bit old, but I thought I should point out that it doesn't need to be a static file to get this working. 

I ran into a similar thing, and it's just a matter of finding that error in your Error.aspx, in our case it was because the masterpage in use relied on a piece of session data and when ResponseRewrite was set the session is not available to our Error.aspx page.

I haven't worked out yet whether this unavailability of session is due to our specific app config or a "by design" part of ASP.net.

blocks|key|1184935|text|我在aspx中构建了一个错误页面，将查询传递给ASP.NET+MVC控制器。您可以将查询重写到此aspx页面，它会将查询传输到您的自定义控制器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1184936|protected+void+Page_Load(object+sender,+EventArgs+e)
{
++//Get+status+code
++var+queryStatusCode+=+Request.QueryString.Get("code");
++int+statusCode;
++if+(!int.TryParse(queryStatusCode,+out+statusCode))
++{
++++var+lastError+=+Server.GetLastError();
++++HttpException+ex+=+lastError+as+HttpException;
++++statusCode+=+ex+==+null+?+500+:+ex.GetHttpCode();
++}
++Response.StatusCode+=+statusCode;

++//+Execute+a+route
++RouteData+routeData+=+new+RouteData();
++string+controllerName+=+Request.QueryString.Get("controller")+??+"Errors";
++routeData.Values.Add("controller",+controllerName);
++routeData.Values.Add("action",+Request.QueryString.Get("action")+??+"Index");

++var+requestContext+=+new+RequestContext(new+HttpContextWrapper(Context),+routeData);
++IController+controller+=+ControllerBuilder.Current.GetControllerFactory().CreateController(requestContext,+controllerName);
++controller.Execute(requestContext);
}|code-block|syntax|javascript|1184937|在这里找到更多详细信息：https://stackoverflow.com/a/27354140/143503|offset|length|1184938|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/27354140/143503^0|0|0|C|17|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

I built an error page in aspx that transfers the query to an ASP.NET MVC controller.
You can rewrite the query to this aspx page and it will transfer the query to your custom controller.

<pre><code>protected void Page_Load(object sender, EventArgs e)
{
 //Get status code
 var queryStatusCode = Request.QueryString.Get("code");
 int statusCode;
 if (!int.TryParse(queryStatusCode, out statusCode))
 {
 var lastError = Server.GetLastError();
 HttpException ex = lastError as HttpException;
 statusCode = ex == null ? 500 : ex.GetHttpCode();
 }
 Response.StatusCode = statusCode;

 // Execute a route
 RouteData routeData = new RouteData();
 string controllerName = Request.QueryString.Get("controller") ?? "Errors";
 routeData.Values.Add("controller", controllerName);
 routeData.Values.Add("action", Request.QueryString.Get("action") ?? "Index");

 var requestContext = new RequestContext(new HttpContextWrapper(Context), routeData);
 IController controller = ControllerBuilder.Current.GetControllerFactory().CreateController(requestContext, controllerName);
 controller.Execute(requestContext);
}
</code></pre>

Find more details here : <a href="https://stackoverflow.com/a/27354140/143503">https://stackoverflow.com/a/27354140/143503</a>

blocks|key|1192229|text|根据@Amila的帖子以及该帖子的确认和完成，我也有同样的问题，我在谷歌上搜索了很多次，但没有机会找到正确的答案。问题是，当你使用ASP.Net+Web+Application时，无论它是不是MVC，你都不能使用Webform+project的旧方法来实现自定义错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1192230|如果你正在使用ASP.Net+Web+Application+(不管它是不是MVC+)，这里有一个选项：|1192231|1192232|在我的场景中，我只想为一个特定的404错误定义一个自定义错误，另一个错误定义为404错误：|blockquote|1192233|1192234|1192235|Senario1:您的自定义页面是一个简单的HTML文件，并放置在root中|BOLD|1192236|<configuration>
+++<system.web>
++++++<customErrors+mode="Off"+/>
+++</system.web>
+++<system.webServer>
+++++++<httpErrors+errorMode="Custom"+existingResponse="Replace">
+++++++++++<remove+statusCode="404"+subStatusCode="-1"+/>
+++++++++++<error+statusCode="404"+path="ErrorPage.html"+responseMode="File"+/>
+++++++</httpErrors>
+++</system.webServer>
</configuration>|code-block|syntax|javascript|1192237|1192238|Senario2:您的自定义页面是一个aspx页面，并放置在root中|1192239|​|1192240|<configuration>
+++<system.web>
++++++<customErrors+mode="Off"+/>
+++</system.web>
+++<system.webServer>
+++++++<httpErrors+errorMode="Custom"+existingResponse="Replace">
+++++++++++<remove+statusCode="404"+subStatusCode="-1"+/>
+++++++++++<error+statusCode="404"+path="ErrorPage"+responseMode="Redirect"+/>
+++++++</httpErrors>
+++</system.webServer>
</configuration>|1192241|注意：由于ASP.net+application中的RouteConfig.cs，我删除了aspx扩展，如果你喜欢，你可以使用ErrorPage.aspx，它是可选的。|1192242|1192243|Senario3:您的自定义页面是一个aspx页面，并放置在[ex:+Page+folder+in+The+root+(~/Page/ErrorPage.aspx)]中|1192244|我注意到，这里的提示是，您不应该使用**~/**进行根寻址；所以我只是在没有~/标记的情况下寻址：|1192245|1192246|<configuration>
+++<system.web>
++++++<customErrors+mode="Off"+/>
+++</system.web>
+++<system.webServer>
+++++++<httpErrors+errorMode="Custom"+existingResponse="Replace">
+++++++++++<remove+statusCode="404"+subStatusCode="-1"+/>
+++++++++++<error+statusCode="404"+path="Page/ErrorPage"+responseMode="Redirect"+/>
+++++++</httpErrors>
+++</system.webServer>
</configuration>|1192247|entityMap^0|1T|N|2O|3|2Y|F|0|7|N|12|3|0|0|0|0|0|0|9|M|4|X|4|0|0|0|0|9|J|4|U|4|0|0|0|0|3|5|J|Q|E|1R|E|0|0|0|9|J|4|U|1H|0|K|2|12|2|0|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1L|8|@$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|1R|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|1T|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1U|8|@$9|1V|A|1W|B|P]|$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|S|7|21|8|@]|D|@]|E|$T|U]]|$1|V|3|-4|5|6|7|22|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|23|8|@$9|24|A|25|B|P]|$9|26|A|27|B|C]|$9|28|A|29|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|2A|8|@]|D|@]|E|$]]|$1|10|3|11|5|S|7|2B|8|@]|D|@]|E|$T|U]]|$1|12|3|13|5|6|7|2C|8|@$9|2D|A|2E|B|P]|$9|2F|A|2G|B|C]|$9|2H|A|2I|B|C]|$9|2J|A|2K|B|C]]|D|@]|E|$]]|$1|14|3|-4|5|6|7|2L|8|@]|D|@]|E|$]]|$1|15|3|16|5|6|7|2M|8|@$9|2N|A|2O|B|P]|$9|2P|A|2Q|B|C]|$9|2R|A|2S|B|C]]|D|@]|E|$]]|$1|17|3|18|5|6|7|2T|8|@$9|2U|A|2V|B|C]|$9|2W|A|2X|B|C]]|D|@]|E|$]]|$1|19|3|Z|5|6|7|2Y|8|@]|D|@]|E|$]]|$1|1A|3|1B|5|S|7|2Z|8|@]|D|@]|E|$T|U]]|$1|1C|3|-4|5|6|7|30|8|@]|D|@]|E|$]]]|1D|$]]

According to @Amila's post and confirmation and completion of that post, I have same problem, I dig a lot google but had no chance to find the correct answer. The problem is when you are working with <code>ASP.Net Web Application</code>, whether it's an <code>MVC</code> or not you can't achieve custom error using the old way with <code>Webform project</code>. 
Here the Option if you are using <code>ASP.Net Web Application</code> (whether it's an <code>MVC</code> or not): 

<blockquote>
 In my scenarios I just want to define a custom error for a specific 404 error, The other error defined same as 404 error:
</blockquote>

 
Senario1: Your custom page is a simple <code>HTML</code> file and placed in the <code>root</code>: 

<pre><code>&lt;configuration&gt;
 &lt;system.web&gt;
 &lt;customErrors mode="Off" /&gt;
 &lt;/system.web&gt;
 &lt;system.webServer&gt;
 &lt;httpErrors errorMode="Custom" existingResponse="Replace"&gt;
 &lt;remove statusCode="404" subStatusCode="-1" /&gt;
 &lt;error statusCode="404" path="ErrorPage.html" responseMode="File" /&gt;
 &lt;/httpErrors&gt;
 &lt;/system.webServer&gt;
&lt;/configuration&gt;
</code></pre>

 <hr>
Senario2: Your custom page is an <code>aspx</code> page and placed in the <code>root</code>: 

<pre><code>&lt;configuration&gt;
 &lt;system.web&gt;
 &lt;customErrors mode="Off" /&gt;
 &lt;/system.web&gt;
 &lt;system.webServer&gt;
 &lt;httpErrors errorMode="Custom" existingResponse="Replace"&gt;
 &lt;remove statusCode="404" subStatusCode="-1" /&gt;
 &lt;error statusCode="404" path="ErrorPage" responseMode="Redirect" /&gt;
 &lt;/httpErrors&gt;
 &lt;/system.webServer&gt;
&lt;/configuration&gt;
</code></pre>

Note: I remove the aspx extension due to <code>RouteConfig.cs</code> in <code>ASP.net application</code>, you can use <code>ErrorPage.aspx</code> if you like, it's optional.
 <hr>
Senario3: Your custom page is an <code>aspx</code> page and placed in the <code>[ex: Page folder in The root (~/Page/ErrorPage.aspx)]</code>: 
The tip here that I noticed is YOU SHOULD NOT USE<code>~/</code> to the root addressing; So I just addresing without <code>~/</code> mark: 

<pre><code>&lt;configuration&gt;
 &lt;system.web&gt;
 &lt;customErrors mode="Off" /&gt;
 &lt;/system.web&gt;
 &lt;system.webServer&gt;
 &lt;httpErrors errorMode="Custom" existingResponse="Replace"&gt;
 &lt;remove statusCode="404" subStatusCode="-1" /&gt;
 &lt;error statusCode="404" path="Page/ErrorPage" responseMode="Redirect" /&gt;
 &lt;/httpErrors&gt;
 &lt;/system.webServer&gt;
&lt;/configuration&gt;
</code></pre>

blocks|key|1184862|text|在我的特殊情况下，我的错误页面有一个母版页，该母版页有一个试图使用会话的用户控件。如果会话不可用，则会得到一个HttpException：“只有在配置文件或页面指令中将enableSessionState设置为true时，才能使用会话状态。”最简单的修复方法是切换到静态html，其次最简单的修复方法是使用更简单的错误页面，最困难的修复方法是难以置信地确保错误页面不做任何假设(例如，会话不会抛出异常)，并且不可能出错。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1184863|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my particular case, my error page had a master page that had a user control that tried to use Session. If Session isn't available, you get an HttpException: "Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive."
Easiest fix is to switch to static html, second easiest fix is to use a simpler error page, hardest fix is to make incredibly sure that your error page makes no assumptions anywhere (like that Session won't throw an exception, for example) and can't possibly error out.

blocks|key|3871895|text|我发现如果你使用redirectMode="ResponseRewrite“，那么你需要在web.config文件的重写区添加一些东西。问题是当你的网站坏了的时候！你不能重写网址，因为你的网站不能调用处理你重写的"virtual.aspx“！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3871896|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have found out that if you use redirectMode="ResponseRewrite" then you need to add something in the rewrite area of the web.config file. Problem is when your site is broken! You can't URL rewrite as your site can't call the "virtual.aspx" that handles your rewrite!

In a old site, I was changing the way that CustomErrors works by adding <code>redirectMode="ResponseRewrite"</code> (new in 3.5 SP1):

<pre><code>&lt;customErrors mode="RemoteOnly" defaultRedirect="Error.aspx" redirectMode="ResponseRewrite"&gt;
 &lt;error statusCode="404" redirect="404.aspx" /&gt;
&lt;/customErrors&gt; 
</code></pre>

The thing is: it shows me the generic error page (the one that you get when you don't set <code>customErrors</code>. If I remove the<code>redirectMode="ResponseRewrite"</code> part, it works fine.

I'm sure 3.5 SP1 is installed in the server, because I use the same setting on other sites hosted in the same server.

Any ideas?

CustomErrors does not work when setting redirectMode="ResponseRewrite"

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在一个老站点中，我通过添加redirectMode="ResponseRewrite" ( 3.5 SP1中的新功能)来改变CustomErrors的工作方式：<customErrors mode="RemoteOnly" defaultRedirect="Error.aspx" redirectMode="ResponseRewrite"> <error statusCode="404"

问将redirectMode=设置为“ResponseRewrite”时CustomErrors不起作用
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将redirectMode=设置为“ResponseRewrite”时CustomErrors不起作用EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将redirectMode=设置为“ResponseRewrite”时CustomErrors不起作用
EN