500.51: A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling.

A configuration or inbound rule execution error occurred.

500.50: A rewrite error occurred during RQ_BEGIN_REQUEST notification handling.

500.24: An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.

500.23: An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.

500.22: An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.

500.15: Direct requests for global.asax are not allowed.

500.12: Application is busy restarting on the web server.

500.11: Application is shutting down on the web server.

Decimal places indicate the cause of the error in more detail: However, if the server has installed Microsoft Internet Information Services (Microsoft IIS), the error code will be specified.

The user only knows that the server has reported an unexpected error. Therefore, at first glance, it is not possible to determine where the error actually lies.

The Internal Server Error 500 is a collective status code for server errors. While the former indicate client errors, the latter are server-related. The situation is different with the 400 and 500 status codes. However, the user never sees this message since the requested content appears instead. If the browser receives the 200 status code, it knows that everything went well. accessing a website) was successful or not. Using status codes, the web server tells an internet user’s browser (client) whether a request (i.e.

5xx server error