Re^4: ModPerl IIS

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.

Comment on Re^4: ModPerl IIS

Replies are listed 'Best First'.
Re^5: ModPerl IIS by ikegami (Patriarch) on Feb 26, 2011 at 00:42 UTC
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]

Replies are listed 'Best First'.

Re^5: ModPerl IIS
by ikegami (Patriarch) on Feb 26, 2011 at 00:42 UTC

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]