You can also set the CGI.pm debug mode to ON, enter the perl debugger, set
the appropriate parameters and set through the file. Sometimes the
results can be different than running through the browser, but other times
it might point out bugs that may not be easily identified by examining the
HTML output.
--Curt
On Thu, 12 Apr 2001, Paul A. Chernoch wrote:
> When I am debugging CGI scripts, I follow this simple approach:
>
> 1. Manually set the CGI environment parameters to simulate a CGI call.
> 2. Invoke the CGI script from the command line on the server.
> 3. Look at the HTML text that is output. If it looks wrong, fix the script.
> (It helps to create a static HTML file on the server that contains all the
> text except the Content-type header to really make sure the HTML is OK.)
> 4. If the HTML that is output looks OK, then create a simple Perl script
> that simply prints out this resulting HTML (with the Content type header)
> to see if that works. If it does not, perhaps your web server requires you
> to fill in more of the HTTP headers than just the content-type? (I have
> seen this happen with some web servers.)
>
> If none of this works, you are on your own...
>
> - Paul
>
> At 07:14 PM 4/11/2001 -0500, Aguztyn Garcia-Cruz wrote:
> >Some body can Help ME?
> >
> >Tanks in Advance
>
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
>
> Paul Anton Chernoch
> Zeborg, Inc.
> 500 West Cummings Park
> Woburn, MA 01801
>
> t: 781.759.0105
> f: 781.935.5090
> c: 781.606.7382
>
> http://www.zeborg.com
> This message is a personal and confidential communication. If you are not
> the intended recipient, please do not read, copy, or use it, and do not
> disclose it to others. Please notify the sender of the delivery error by
> replying to this message, and then delete it from your system. Thank you.
>
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
>
>
>
