IIS 6.0 does not display Perl Debugging info in browser

I have been testing IIS 6.0 for a future upgrade from IIS 5.0. IIS 6.0 is not returning debugging info to the browser when IIS 5.0 did. For example, I will execute a Perl script in an CGI Executable directory in IIS 6.0 that uses a module that is not installed on the server. This is what it returns:

========================
CGI Error
The specified CGI application misbehaved by not returning a complete set of HTTP headers.

If I run the same script on IIS 5.0, this is what is returns:

CGI Error
The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are:

Can't locate Gettext.pm in @INC (@INC contains: C:/Perl/lib C:/Perl/site/lib .) at C:\Websites\secure\cgi-bin\test2.pl line 1.
BEGIN failed--compilation aborted at C:\Websites\secure\cgi-bin\test2.pl line 1.
========================

This may seem like a trivial thing, but it actually turns a quick debug operation into a surprisingly time consuming process, especially when you need to debug a lot of problems.

Check with your Perl vendor.

I did, and they said that it's because IIS 6 now REQUIRES that a Content-type header be returned, so I added a header within a BEGIN {} in the code in hopes that would get the header out before the compilation error. That got rid of the CGI Error, but there was still no output to the browser (blank screen). I have not been able to find a setting in IIS or the registry that controls the necessity of headers for CGI programs, but I have doubts that is even the problem.

Also, I am running the exact same installation of Activestate Perl (5.6.1 Build 628) on Win2k3 as I am on Win2k, so this is definately a change in behavior in IIS 6 or Win2k3 from IIS 5/win2k.

I haven't used Perl since back when NT4.0 was the new kid on the block, and I don't have IIS6. How's that for a lot of help?

Perhaps someone who knows will jump in on your questions here.

I'm having this same problem after upgrading from IIS5 to IIS6. Did you ever get this resolved?

We are also having the same issue. I need to see the output of those scripts! On Windows Server 2003 in this case it was a fresh install of IIS 6 on a new server, but we copied the entire web root from an old IIS 5 install (on windows 2000) to the new server, and just pointed the web root to the copied directory. Still though, this seems like a basic requirement for people trying to develop and debug CGI scripts. Surely there is a setting somewhere? Maybe this is something found in the deep dark magic of Metabase?

The only solution I found was to rename the file by adding a "nph-" in front of the file name. This is for debugging.

Monty