Question

我们通常在全球的轴心中追捕未经处理的例外情况,然后改用一个无害冰的错误页。这对生计环境来说是好的,但是在我们的发展环境中,我们要检查的是,如果是的话,习俗错误就会落空。

是否容易检查习俗错误是否通过法律予以抵消?

Answer 1

Yep, 途径:。

System.Configuration.Configuration configuration =
    System.Web.Configuration.WebConfigurationManager.OpenWebConfiguration("/");

System.Web.Configuration.CustomErrorsSection section =
    (CustomErrorsSection)configuration.GetSection("system.web/customErrors");

一旦有了这一节,你就可以检查该模式是否具备:

CustomErrorsMode mode = section.Mode;
if (mode == CustomErrorsMode.Off)
{
    // Do something
}

Answer 2

我建议使用以下财产:

HttpContext.Current.IsCustomErrorEnabled

参看 , IsCustom 不可撤销的考虑更像遥感考虑:

The IsCustomErrorEnabled property combines three values to tell you whether custom errors are enabled for a particular request. This isn t as simple as reading the web.config file to check the section. There s a bit more going on behind the scenes to truly determine whether custom errors are enabled.

财产看着这三种价值观:

The web.config s < deployment > section s retail property. This is a useful property to set when deploying your application to a production server. This overrides any other settings for custom errors.

The web.config s < customErrors > section s mode property. This setting indicates whether custom errors are enabled at all, and if so whether they are enabled only for remote requests.

The HttpRequest object s IsLocal property. If custom errors are enabled only for remote requests, you need to know whether the request is from a remote computer.

Answer 3

这应当做到......

using System.Web.Configuration;
using System.Configuration;

// pass application virtual directory name
Configuration configuration = WebConfigurationManager.OpenWebConfiguration("/TestWebsite");
CustomErrorsSection section = (CustomErrorsSection)configuration.GetSection("system.web/customErrors");
CustomErrorsMode mode=section.Mode;

友情链接