A quick look at CGI shows them using -NAME,-VALUE, and -COOKIE all in all lower case. I'm not sure if CGI is doing some magic that makes it not care about case, but I would recommend using the same as they use in the documentation to keep things simple.

For logins I general check for success and do the right thing then. Instead of checking for failure and doing the login. Its definitly personal preference but it can help weed out some bugs where variables aren't what you expect. Aslo CGI::Carp might be of some use for you. It will let you send warnings to the browser so that you can use them for debuging. This can be usefull when you don't have access to the error_log.


___________
Eric Hodges

In reply to Re: CGI login issues by eric256
in thread CGI login issues by sulfericacid

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.