"Jay Blanchard" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] [snip] ....stuff.... [/snip]
>From http://www.w3.org/TR/html4/interact/forms.html#h-17.13.1 17.13.1 Form submission method The method attribute of the FORM element specifies the HTTP method used to send the form to the processing agent. This attribute may take two values: get: With the HTTP "get" method, the form data set is appended to the URI specified by the action attribute (with a question-mark ("?") as separator) and this new URI is sent to the processing agent. post: With the HTTP "post" method, the form data set is included in the body of the form and sent to the processing agent. The "get" method should be used when the form is idempotent (i.e., causes no side-effects). Many database searches have no visible side-effects and make ideal applications for the "get" method. If the service associated with the processing of a form causes side effects (for example, if the form modifies a database or subscription to a service), the "post" method should be used. Note. The "get" method restricts form data set values to ASCII characters. Only the "post" method (with enctype="multipart/form-data") is specified to cover the entire [ISO10646] character set. I'm begining to see. The definitions of $_POST and $_GET are word for word identical as predefined variables: http://ca.php.net/reserved.variables However they are designed to be paired with post and get form methods, the $_GET to be used with <a href > query string (after the '?' in a url) as mentioned in the page you supplied above (reposted below): http://www.w3.org/TR/html4/interact/forms.html#h-17.13.1 So apparently, one of the morals to the story is that the $_GET method is more prone to security breach? I still don't see the whole picture, but for what I'm doing now I don't really need to. Dale -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
