in reply to Re^2: ModPerl IIS
in thread ModPerl IIS

I don't know if it CGI, mod_perl.

There's not much I can do about it if you didn't believe me the first time around.

the error message is like what you said..

Then the solution is like what I said. I'm not sure what else you want from me. You didn't ask any new question or indicate any new problem.

Replies are listed 'Best First'.
Re^4: ModPerl IIS
by Kargil Jay (Initiate) on Feb 25, 2011 at 21:09 UTC 
    sorry, my bad english.. I wanted to say 'I did not know before hearing from you, if it is CGI/mod_perl'.. but rather conveyed 'I don't know if it CGI, mod_perl' . 

Now I am sure, it is IIS . Not mod_perl but CGI with Templates.

Now Could some monk please throw light in 
    sorry, my bad english.. I wanted to say 'I did not know before hearing from you, if it is CGI/mod_perl'.. but rather conveyed 'I don't know if it CGI, mod_perl' . 

Now I am sure, it is IIS . Not mod_perl but CGI with Templates.

Now Could some monk please throw light,  in what kind of environment I can use to debug this? IDE etc.
[reply]

      Already answered.

      Then the solution is like what I said.

      The error is that you didn't return a proper CGI response. You should use the CGI module and use its header method to create the proper headers.

      If you are doing that, it could be that some error (possibly a compile-time error) occurred before your call to header had a chance to execute. If so, this should be logged in your web server's error log. If not, it's a question of configuring your web server (which has nothing to do with Perl). Alternative, you may be able to redirect error messages to the screen using CGI::Carp. 

      use CGI::Carp qw( fatalsToBrowser );

      [download]
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom