in reply to Re: Checking input
in thread Checking input

I haven't tried anything yet, I couldn't find any information about how to. I couldn't get Pardus' suggestions to work. Returned internal server error even when using CGI::Carp qw(fatalsToBrowser). - Neil

Replies are listed 'Best First'.
Re: Checking input
by Abigail-II (Bishop) on Feb 25, 2003 at 17:09 UTC
    No idea at all? It looks like you haven't met one of the most fundamental cornerstones of the Perl language: regular expressions. Study the manual pages, or a book.

    And learn the language from the command line, don't try to learn it via CGI.

    Abigail

Re: Re: Re: Checking input
by BrowserUk (Patriarch) on Feb 25, 2003 at 21:01 UTC

    A tip to reenforce [Abigail's sentiments:

    You can test your CGI scripts by running them from the command line before you deploy them. If the script needs command line parameters, supply them via the command line as well. If you pipe the output to a file, you can check the results by looking at the out with a browser. The best bit is that you will see any compiletime or runtime errors at the terminal rather than having to search the logs

    See the CGI.pm code for more info.


    ..and remember there are a lot of things monks are supposed to be but lazy is not one of them

    Examine what is said, not who speaks.
    1) When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong.
    2) The only way of discovering the limits of the possible is to venture a little way past them into the impossible
    3) Any sufficiently advanced technology is indistinguishable from magic.
    Arthur C. Clarke.