Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am developing a Perl script using FastCGI (using CGI::Fast and CGI::Carp 'fatalsToBrowser').
When my script has compile errors, it causes the browser to hang. It seems that fatalsToBrowser is not working the way it does with normal CGI (just send the compile errors to the browser). How can I fix this?
I’m the CGI.pm maintainer. I would recommend avoiding using ‘fatalsToBrowser’ in this case. Some Perl frameworks over features which do the same thing. For example, with CGI::Application there is CGI::Application::Plugin::DebugScreen. Other frameworks have something similar.
In other cases, the popular ‘Carp’ and ‘CGI::Carp’ modules can conflict if they both end up imported in the same name space, because they both provide functions with the same names, like ‘carp’ and ‘croak’. I recommend using Carp and avoiding CGI::Carp.