Debugging a CGI Script

Tony Wasson plug-discuss@lists.plug.phoenix.az.us
Fri, 10 May 2002 07:55:02 -0000


I always thought you *test* with -w and get everything coded right and then
run without it.
No, I am not a perl hacker. ;-)

Tony Wasson


----- Original Message -----
From: "George Toft" <george@georgetoft.com>
To: <plug-discuss@lists.plug.phoenix.az.us>
Sent: Friday, May 10, 2002 12:05 PM
Subject: Re: Debugging a CGI Script


> Hi Vic,
>
> Victor Odhner wrote:
> [snip]
> > Debugging at the command line allows you to use
> > the -w option (which you should NOT use in a
> > production CGI), and even the Perl debugger, to
> > diagnose problems in your CGI.  This is especially
> > needed if the script is aborting on you, in which
> > case the Apache error log often isn't a lot of help.
>
> Can you expound on this?  My first Perl/CGI book said you should
> always use the -w flag in a CGI script for security reasons.
>
> Thank you.
>
> George
> ________________________________________________
> See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't
post to the list quickly and you use Netscape to write mail.
>
> PLUG-discuss mailing list  -  PLUG-discuss@lists.plug.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>