Display or view the perl cgi errors in a web browser

by on June 13, 2007 · 5 comments· LAST UPDATED June 17, 2007

in , ,

Q. I’m currently learning Perl cgi programming and coded a small web site in a Perl. Usually errors are logged in a log file. How can I view the perl cgi errors in a we browser like firefox?

A. CGI scripts have a nasty habit of leaving warning messages in the error logs that are neither time stamped nor fully identified. Tracking down the script that caused the error is a pain.

You need to install and use CGI::Carp module.

With this module the standard warn(), die (), croak(), confess() and carp() calls will automatically be replaced with functions that write out nicely time-stamped messages to the HTTP server error log.

You can also log message to a browser. Now add following two lines before sending any headers to a browser:

use CGI;
use CGI::Carp qw(warningsToBrowser fatalsToBrowser); 

With above lines it is possible to make non-fatal errors appear as HTML comments embedded in the output of your program. To enable this feature, export the new "warningsToBrowser" subroutine. Since sending warnings to the browser before the HTTP headers have been sent would cause an error, any warnings are stored in an internal buffer until you call the warningsToBrowser() subroutine with a true argument.

See official CGI::Carp man page for more information.

TwitterFacebookGoogle+PDF versionFound an error/typo on this page? Help us!

{ 5 comments… read them below or add one }

1 Luke June 16, 2007 at 8:40 pm

Hi Vivek,
Just pointing out a typo at the end of your post – isn’t it called CGI::Carp, and not CGI::Crap? You seem to have mispelled your link to the man page(although the link still works).

Reply

2 nixCraft June 17, 2007 at 9:13 am

Luke,

Thanks for the heads up! FAQ has been updated.

Reply

3 Mimi November 24, 2011 at 3:39 am

Thanks! Useful!

Reply

4 Craig June 13, 2012 at 9:00 am

This article is no longer valid with the new versions of perl.

I have moved to IIS7 and ActivePerl 5.14 and fataltobrowsers no longer works.

all you get is a 500 INTERNAL SERVER ERROR!

Reply

5 Sam June 27, 2012 at 3:18 am

Thanks! Very useful.

Reply

Leave a Comment

Tagged as:

Previous Faq:

Next Faq: