People keep saying this, but overlook that CGI::Carp has a convenient mechanism to control what gets sent to the browser with fatalsToBrowser activated: 

#!/usr/bin/perl
                                                                      
+          
use strict;
                                                                      
+          
use CGI::Carp qw(fatalsToBrowser set_message);
                                                                      
+          
                                                                      
+          
my $sub_message = sub {
                        my ($message) = @_;
                        if ($ENV{REMOTE_ADDR} eq '127.0.0.1')
                        {
                           print "Oops: $message";
                        }
                        else
                        {
                           print "Unable to process, please try later"
+;
                        }
                     };
                                                                      
+          
set_message($sub_message);
                                                                      
+          
die "aiee!";

[download]
Of course you can use whatever condition you like to control whether the text of the die message gets displayed or not - a debugging flag or similar might make more sense in some circumstances.

fatalsToBrowser provides a simple mechanism for trapping exceptions in the code which might otherwise result in at best a confusing 500 status in the users browser, and the advantage of doing something like the above is that you can use the same code for debugging as you do in production thus reducing the possibility of introducing new bugs when removing diagnostic code.

You should bear in mind that not everyone has the luxury of access to the error logs when deploying a web application to production, indeed some servers (such as IIS) make it very difficult to get that information.

/J\

In reply to Re^2: Stopping Module Croaking by gellyfish
in thread Stopping Module Croaking by allyc

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.