ok, I see here you can also change the http status response code. This is also useful.
Sent by FoxWeb Support on 04/14/2015 03:14:13 PM:
Are you asking for information on how to customize these errors, or how to trap them? By default "stub" errors (as opposed to VFP script errors) have a 200 HTTP status. If you want to return status 500 instead, you can add a new registry value to the same key I specified in my previous response:
StubErrorStatus500 = "1"
Note that this must be a string (REG_SZ) value.
FoxWeb Support Team
Sent by Steve Moore on 04/14/2015 03:07:08 PM:
Clarification: I understand how to create the IIS7 pages, I guess what I'm really asking is what http response codes can In expect from these pages? Is there an easy way to trap these errors?
Sent by Steve Moore on 04/14/2015 02:59:11 PM:
Can you point me to some specific information on returning alternate error pages for "foxweb not started", "foxweb no channels active" and "foxweb timed out" errors in IIS7?