Question

I’ve seen servers return 500 Internal Server Error codes with extra ‘detail’ in a decimal-delimited sub-code, e.g. 500.19.

Is this sub-code standardised or can I freely use it? How do I prevent crashing into vendor codes, say, in IIS or ASP.NET?

Luke

Answer 1

There is a Microsoft standard list. See – http://support.microsoft.com/kb/943891

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 500 error:

• 500.0 – Module or ISAPI error occurred.
  • 500.11 – Application is shutting down on the web server.
  • 500.12 – Application is busy restarting on the web server.
  • 500.13 – Web server is too busy.
  • 500.15 – Direct requests for Global.asax are not allowed.
  • 500.19 – Configuration data is invalid.
  • 500.21 – Module not recognized.
  • 500.22 – An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
  • 500.23 – An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.
  • 500.24 – An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
  • 500.50 – A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
  • Note Here is where the distributed rules configuration is read for both inbound and outbound rules.
  • 500.51 – A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
  • Note Here is where the global rules configuration is read.
  • 500.52 – A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
  • 500.53 – A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.
  • 500.100 – Internal ASP error.