500 VS 500.100错误经典ASP
当在IIS7运行传统的ASP应用中，当将一个500错误发生，而不是500.100错误？我的意思是，但不是500.100错误出现500错误。我是IM pression，当错误发生在它的VBScript中code传统的ASP只会扔500.100错误之下。
通过一个例子来解释一下将是非常有益的。
When running classic ASP application in IIS7, when would a 500 error happen rather than a 500.100 error? What I mean is that a 500 error occurs but not a 500.100 error. I am under the impression that classic ASP would only throw 500.100 errors when error occurs in it's VBScript code. Some explanation through an example would be very helpful.
经典ASP始终返回 500.100 状态，如果有一个脚本错误。它已经像在IIS中的previous版本很长的时间和行为并没有改变。
Classic ASP has always returned a 500.100 status if there is a script error. It's been like for a very long time in previous versions of IIS and the behaviour hasn't changed.
如果你想赶上传统ASP脚本错误的和的能够阅读 Server.GetLastError（）对象在您的自定义错误页面（说的记录），你需要专门为提供处理器500.100 。
If you want to catch Classic ASP script errors and be able to read the Server.GetLastError() object in your custom error page (say for logging) you need to provide a handler specifically for 500.100.
如果您不指定一个自定义的 500.100 错误，则IIS将回落到您的自定义（或其自身） 500 错误页，但 Server.GetLastError（）不会提供有关错误的任何有用的信息。
If you don't specify a custom 500.100 error then IIS will fall back to your custom (or its own) 500 error page but Server.GetLastError() won't provide any useful information about the error.