500 internal bug in IIS 7

The impression that this famous bug hint has existed since the ASP era

I don't know how to think about it.

There are a number of developers in the group of people you face.

In addition to the wrong environment for the developers is basically a

Why not set these as "Factory defaults"?

It's been a few years, a little bit

Break the pattern and get back to the problem.

First, the following items are required for activation:

1. Send the bug to the browser

2. Activate server-side bug

3. Activation of client-side reconnaissance

4. Activating the parent path (not necessary)

Two, wrong page related

1. Point 500 wrong page to%systemdrive%\inetpub\custerr\<language-tag>\500-100.asp

2. Set the 500 bug function to the "detailed bug"

Third, the management interface on the left side of the platform root, as well as the root of the "Web site" to do the above settings.

500 internal bug in IIS 7