Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Common mistake (Score:2, Interesting)

    by essuu (3384) on 2002.10.09 6:45 (#13705) Journal

    We (the programmers) all know why a GET request that is non-idempotent is bad but a lot of books on html seem to propogate the notion that you can use GET and POST interchangably except when

    • Sending passwords
    • Sending lots of data
    • Uploading files
    How many html coders (of the type to need nms) do you know that have read the http specs ? Perhaps the error message could explain a bit about why it is bad or link to more detail on the nms website.

    Error: GET request not permitted

    You should never use GET when asking a webserver to do something
    like submitting an email or updating a database. The url can be cached by a users browser or by a web proxy and the results may not be what you expect.

    Learn more about this at http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.1 or on the nms website at [insert url here].

    To configure your form to run with FormMail, you need to set the request method to POST in the opening form tag, like this:

    <form action="/cgi-bin/FormMail.pl" method="post">
    • I'd say tone it way down, with a pointer to an explanation of "why" online. Just explain "what."

      Your HTML form says something like this:
      <form action="/cgi-bin/FormMail.pl" method="get">
      This is an error; please see http://...
      Change it to something like this:
      <form action="/cgi-bin/FormMail.pl" method="post">
      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
      • I think it's more likely that the erroneous form tag wouldn't have an action attribute at all -- at least, the error message needs to address that possibility.