All geek questions in one place

500 Vs 500.100 Error in classic ASP

When starting a classic ASP application in IIS7, when does 500 error happen, and not 500.100 error? I mean that error 500 occurs, but not error 500.100. I get the impression that the classic ASP will only throw 500.100 errors when VBScript code appears in it. Some example explanation would be very helpful.

+6
source share
1 answer

Classic ASP always returned status 500.100 if there is a script error. This was a very long time in previous versions of IIS, and the behavior has not changed.

If you want to catch Classic ASP script errors and be able to read the Server.GetLastError() object on your user errors page (say, for logging), you need to provide a handler specifically for 500.100 .

If you do not specify a custom error 500.100 , then IIS will return to your own page (or its own) 500 , but Server.GetLastError() will not provide any useful error information.

+8
source

Source: https://habr.com/ru/post/909087/

More articles:


All Articles