IIS7 has a simple method of allowing specific debug errors instead of generic 500 errors on remote computers (errormode=detailed & scriptErrorSentToBrowser=t
rue). I'm looking for a way to do the same on IIS6.
This is a win2k3 development box running IIS6. Debugging is for PHP installed as fastcgi. When PHP is installed as an isapi, error handling is left to PHP - no issue. M$'s fastcgi is intercepting php cgi errors and throwing generic 500's instead (unless I logon to the server and view the page locally - full debug info available then).
How do I get IIS6 to display debugging errors on remote/client computers just like it does locally?
I can't upgrade PHP becuase the version is matched to the live server and the live server is cPanel. I can't use isapi as a work-around because I'm using fastcgi as a freeking work-around for this problem:-
I've seen a lot of solutions for iis7 - nothing or iis6.