• version 1 - roll your own everything (a) headers, (b) html, (c) parsing, (d) file i/o
  code - run it
• version 2 - use CGI.pm for parameters, some html, and a tied DB_File for persistence.
  (This particular use of the tied hash is disappointing slow - I think I'm doing exactly the wrong thing with it here. But for many purposes these things can be very nice.)
  code - run it
• cookie.cgi - use CGI.pm for parameters and getting/setting the cookie.
  code - run it
  Pay particular attention to the order in which the cookie stuff happens - when you can read a cookie, when you can write a cookie, and how that can interact with form (or hidden) values.

• "Forbidden - you don't have permission..." - usually means that the file hasn't been made executable, "chmod +x filename".
• httpd must have read access on directories, execute access on file - if its creating/changing files, remember it doesn't run as you but as the web server

• Run it from the command line.
• If you're using CGI.pm, can do "./script.cgi key=value key2=value2" to set parameters when you're invoking it.
• Look in httpd error log, i.e. "tail /home/httpd/log/error_log"

• "use CGI::Carp qw(fatalsToBrowser);"
• or run from the command line with name=value pairs
• or put in lots of html-ish "print" statements to see what's going on. (But don't forget to do "Content-type: text/html" if somewhere before "print".)

You don't have to include cookies, perhaps to record a user's preferences, but I encourage you to do so if you'd like to see how the work.

If you don't have a project in mind, write something that a database of user names, phone numbers, and email addresses. Include a way to add a new user to the database.