There is no such thing as a $_GET
array or a $_POST
array - at least, not according to the HTTP specifications. These superglobals are merely constructs offered by PHP to make your life more "convenient".
The problem with $_GET
and $_POST
is that despite their names, they don't actually have anything to do with the request methods GET
and POST
at all. Rather, $_GET
retrieves variables from the URL query string, while $_POST
retrieves variables submitted as part of a form. For some reason, PHP has arbitrarily tangled up the data representation with the request method. Not to mention that global variables are a terrible idea in general!
Fortunately, Slim saves the day by providing a more HTTP-friendly way of accessing data supplied by the request. Rather than thinking in terms of "GET parameters" and "POST parameters", we should think in terms of the different components of the HTTP request. Recall that a request consists of a url, method, headers, and optionally, a body - any of these could potentially contain data that we'd want to get at in one of our controller methods.
There are really two places in the URL that could contain information we'd want to retrieve - the path itself, and the query string.
Variables that we'd want to retrieve from the path itself are typically declared in the route definition. These can be retrieved directly from the $args
array by indexing it with the name of the placeholder. For example, suppose we have a route defined as:
$app->get('/api/users/u/{user_name}', function (Request $request, Response $response, array $args) {
...
});
If someone submits a request to /api/users/u/david
, then the value 'david'
will be available at $args['user_name']
.
The other place where we'd typically find client-supplied data is in the query string (the part of the URL after the ?
). In this case, we can access these variables through the $request
parameter, using the getQueryParams
method:
// request was GET /api/users/u/david?format=json
$params = $request->getQueryParams();
// Displays 'json'
echo $params['format'];
GET
requests through the query string. Again, this does not mean that query strings == GET.Slim provides a number of methods for retrieving data from the body. The two most common scenarios involve retrieving data that was submitted from a form, and uploaded files.
To get client-submitted form data, simply use the getParsedBody()
method on $request
:
// request was POST /api/users, with form values user_name => 'kevin' and password => 'hunter2'
$params = $request->getParsedBody();
// Displays 'kevin'
echo $params['user_name'];
POST
requests through the message body, but this does not mean that message body and POST are equivalent concepts.To get at files that have been encoded in the HTTP request body (for example using an HTML <input type='file' ...
element), use the getUploadedFiles()
method:
$files = $request->getUploadedFiles();
To retrieve request headers, use $request->getHeaders()
, $request->getHeader()
, or $request->getHeaderLine()
. See Slim's documentation for more information.
Usually, you'll already know the HTTP method by the time you've started executing code in your controller, because it will be explicitly mentioned in your route definition. Nonetheless, there are circumstances when you need to determine the HTTP method dynamically:
$method = $request->getMethod();