On 2/24/12 4:55 PM, Jeremiah Dodds wrote:
Except that per HTTP, GET and POST are completely different operations. One
is idempotent and cacheable, the other is not idempotent and not cacheable.
I very much care which someone is using.
Correct me if I'm wrong, but you're referring to the HTTP *method*
used. A POST can be made to a URL that includes a query-string, but
what that means as far as interpreting the variables is undefined as
far as I know.
Because of that, I think it's a bad idea to either treat them as the
same thing, or rely on both $_POST and $_GET parameters being present.
The underlying problem is that HTTP has a URI query string, and a body.
In a typical GET request there is no body. In a typical POST the body
is a query string in similar format to the URI's query string, plus
possibly other stuff. In other request methods the body may be
something else entirely.
PHP's superglobals make the (wrong) assumption that the URI query string
comes from a GET query (hence $_GET) and body comes from a POST query
string ($_POST), because that matches up with the default method=""
attribute of HTML forms. That assumption is limiting and misleading,
and made worse by the existence of $_REQUEST, but is the assumption that
PHP makes.
--Larry Garfield
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
