抛出HttpException总是发回HTTP 500错误？ [英] Throwing an HttpException always sends back HTTP 500 error?

问题描述

我想抛出一个HTTP 403错误code回到了客户端。我读过HttpException是实现这个最彻底的方法，但它不是为我工作。我抛出异常在页面中是这样的：

I'm trying to throw an HTTP 403 error code back at the client. I've read that HttpException is the cleanest way to accomplish this, but it's not working for me. I throw the exception from within a page like this:

throw new HttpException(403,"You must be logged in to access this resource.");

然而，这只会给一个标准的ASP.Net堆栈跟踪（500错误）时的customErrors是关闭的。如果是的customErrors上，那么这将不会重定向到我时出现403错误要显示设置页面。我应该忘记HttpException，而是设置所有的HTTP codeS自己？我该如何解决这个问题？

However, this will only give a standard ASP.Net stack trace(with 500 error) when CustomErrors is off. If CustomErrors is on, then this will not redirect to the page I have setup to be displayed when a 403 error occurs. Should I forget about HttpException and instead set all the HTTP codes myself? How do I fix this?

我的web.config的自定义错误的部分是：

The custom errors part of my Web.Config is this:

<customErrors mode="On" defaultRedirect="GenericErrorPage.html">
      <error statusCode="403" redirect="Forbidden.html" />
</customErrors>

非但没有Forbidden.html，我会得到GenericErrorPage.html

Instead of getting Forbidden.html, I'll get GenericErrorPage.html

推荐答案

其实我已经结束了做我自己的漂亮的小类来解决这个问题。它不处理一切，我不知道它玩弄MVC不错，但它为我所用。基本上，而不是依赖于ASP.Net输出正确的错误页面和错误code，它会清除错误，然后做一个服务器端的传输和显示相应的Web.Config错误页面。它还可以识别的customErrors模式，并相应地作出反应。

I've actually ended up making my own nifty little class to fix this problem. It doesn't handle everything and I'm not sure it plays nice with MVC, but it works for my use. Basically, instead of relying on ASP.Net to output the correct error page and error code, it will clear the error and then do a server-side transfer and display the appropriate Web.Config error page. It also recognizes the customErrors mode and reacts accordingly.

public static class CustomErrorsFixer
{
    static public void HandleErrors(HttpContext Context)
    {
        if(RunIt(Context)==false){
            return;
        }
        HttpException ex = Context.Error as HttpException;
        if(ex==null){
            try{
                ex=Context.Error.InnerException as HttpException;
            }catch{
                ex=null;
            }
        }

        if (ex != null){
            Context.Response.StatusCode = ex.GetHttpCode();
        }else{
            Context.Response.StatusCode = 500;
        }
        Context.ClearError();

        Context.Server.Transfer(GetCustomError(Context.Response.StatusCode.ToString()));
        HttpContext.Current.Response.End();
    }
    static protected string GetCustomError(string code)
    {
        CustomErrorsSection section = ConfigurationManager.GetSection("system.web/customErrors") as CustomErrorsSection;

        if (section != null)
        {
            CustomError page = section.Errors[code];

            if (page != null)
            {
                return page.Redirect;
            }
        }
        return section.DefaultRedirect;
    }
    static protected bool RunIt(HttpContext context){
        CustomErrorsSection section = ConfigurationManager.GetSection("system.web/customErrors") as CustomErrorsSection;
        switch(section.Mode){
            case CustomErrorsMode.Off:
                return false;
            case CustomErrorsMode.On:
                return true;
            case CustomErrorsMode.RemoteOnly:
                return !(context.Request.UserHostAddress=="127.0.0.1");
            default:
                return true;
        }
    }

}

然后将其激活，只需添加一个小东西Global.asax中

And then to activate it, just add a small thing to Global.asax

    protected virtual void Application_Error (Object sender, EventArgs e)
    {
        CustomErrorsFixer.HandleErrors(Context);
    }

这篇关于抛出HttpException总是发回HTTP 500错误？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！