In IIS I can configure my custom error pages.
For each HTTP Error code I can say where to go. Several codes have a number of "sub" codes available. For example 404 has a regular 404, 404;1, 404;2 and so on..
在IIS中,我可以配置自定义错误页面。对于每个HTTP错误代码,我可以说要去哪里。几个代码有许多“子”代码可用。例如,404具有常规404,404; 1,404; 2等等。
What are they for? When are they returned? Should I make custom pages for these errors? Can I somehow easely configure all code "families" to come to the same page?
它们适用于什么?他们什么时候回来的?我应该为这些错误制作自定义页面吗?我可以以某种方式轻松配置所有代码“家庭”来到同一页面?
3 个解决方案
#1
21
401 - Access denied. IIS defines several different 401 errors that indicate a more specific cause of the error. These specific error codes are displayed in the browser but are not displayed in the IIS log:
401 - 访问被拒绝。 IIS定义了几个不同的401错误,这些错误表明错误的更具体原因。这些特定的错误代码显示在浏览器中,但不会显示在IIS日志中:
- 401.1 - Logon failed.
- 401.2 - Logon failed due to server configuration.
- 401.3 - Unauthorized due to ACL on resource.
- 401.4 - Authorization failed by filter.
- 401.5 - Authorization failed by ISAPI/CGI application.
- 401.7 – Access denied by URL authorization policy on the Web server (This error code is specific to IIS 6.0.)
401.1 - 登录失败。
401.2 - 由于服务器配置登录失败。
401.3 - 由于资源上的ACL而未经授权。
401.4 - 过滤器授权失败。
401.5 - ISAPI / CGI应用程序授权失败。
401.7 - Web服务器上的URL授权策略拒绝访问(此错误代码特定于IIS 6.0。)
Here is the complete list in the MSDN documentation for IIS 5.0 and 6.0 and for IIS 7.0, 7.5 and 8.0.
以下是IIS 5.0和6.0以及IIS 7.0,7.5和8.0的MSDN文档中的完整列表。
If you want to show your visitors or users a nice custom message depending on these subcode, you could do it. But you needn't.
如果您想根据这些子代码向访问者或用户显示一个不错的自定义消息,您可以这样做。但你不需要。
#2
5
"Substatus" error codes are specific to IIS. They are for "internal" logging purposes - whatever the substatus code, it is the the parent error that gets returned to the client (404.2 gets sent back as 404)
“Substatus”错误代码特定于IIS。它们用于“内部”日志记录 - 无论子代码如何,它都是返回给客户端的父错误(404.2以404发回)
They were implemented specifically to reduce the surface area of attack of IIS whilst still providing sysadmins with a meaningful amount of data. Therefore you actively should not send back specific substatus error messages as you will be opening your IIS installation to possible attack.
它们专门用于减少IIS的表面攻击区域,同时仍为系统管理员提供有意义的数据量。因此,您将主动不应发回特定的子状态错误消息,因为您将打开IIS安装以进行可能的攻击。
#3
0
This blog article appears to explain a lot of this. Perhaps it can be of help? At the very least, it explains the meaning of the 'sub-codes'.
这篇博客文章似乎解释了很多这方面的内容。也许它可以有所帮助?至少,它解释了“子代码”的含义。
#1
21
401 - Access denied. IIS defines several different 401 errors that indicate a more specific cause of the error. These specific error codes are displayed in the browser but are not displayed in the IIS log:
401 - 访问被拒绝。 IIS定义了几个不同的401错误,这些错误表明错误的更具体原因。这些特定的错误代码显示在浏览器中,但不会显示在IIS日志中:
- 401.1 - Logon failed.
- 401.2 - Logon failed due to server configuration.
- 401.3 - Unauthorized due to ACL on resource.
- 401.4 - Authorization failed by filter.
- 401.5 - Authorization failed by ISAPI/CGI application.
- 401.7 – Access denied by URL authorization policy on the Web server (This error code is specific to IIS 6.0.)
401.1 - 登录失败。
401.2 - 由于服务器配置登录失败。
401.3 - 由于资源上的ACL而未经授权。
401.4 - 过滤器授权失败。
401.5 - ISAPI / CGI应用程序授权失败。
401.7 - Web服务器上的URL授权策略拒绝访问(此错误代码特定于IIS 6.0。)
Here is the complete list in the MSDN documentation for IIS 5.0 and 6.0 and for IIS 7.0, 7.5 and 8.0.
以下是IIS 5.0和6.0以及IIS 7.0,7.5和8.0的MSDN文档中的完整列表。
If you want to show your visitors or users a nice custom message depending on these subcode, you could do it. But you needn't.
如果您想根据这些子代码向访问者或用户显示一个不错的自定义消息,您可以这样做。但你不需要。
#2
5
"Substatus" error codes are specific to IIS. They are for "internal" logging purposes - whatever the substatus code, it is the the parent error that gets returned to the client (404.2 gets sent back as 404)
“Substatus”错误代码特定于IIS。它们用于“内部”日志记录 - 无论子代码如何,它都是返回给客户端的父错误(404.2以404发回)
They were implemented specifically to reduce the surface area of attack of IIS whilst still providing sysadmins with a meaningful amount of data. Therefore you actively should not send back specific substatus error messages as you will be opening your IIS installation to possible attack.
它们专门用于减少IIS的表面攻击区域,同时仍为系统管理员提供有意义的数据量。因此,您将主动不应发回特定的子状态错误消息,因为您将打开IIS安装以进行可能的攻击。
#3
0
This blog article appears to explain a lot of this. Perhaps it can be of help? At the very least, it explains the meaning of the 'sub-codes'.
这篇博客文章似乎解释了很多这方面的内容。也许它可以有所帮助?至少,它解释了“子代码”的含义。