$_POST

(PHP 4 >= 4.1.0, PHP 5, PHP 7, PHP 8)

$_POSTHTTP POST variables

Descrizione

An associative array of variables passed to the current script via the HTTP POST method when using application/x-www-form-urlencoded or multipart/form-data as the HTTP Content-Type in the request.

Esempi

Example #1 $_POST example

<?php
echo 'Hello ' . htmlspecialchars($_POST["name"]) . '!';
?>

Assuming the user POSTed name=Hannes

Il precedente esempio visualizzerà qualcosa simile a:

Hello Hannes!

Note

Nota:

Questa è una variabile 'superglobale', o automaticamente global. Ciò semplicemente significa che è visibile in tutti gli ambiti in uno script. Non è necessario dichiararla come global $variable; per accedervi da funzioni o metodi.

add a note add a note

User Contributed Notes 6 notes

up
274
james dot ellis at gmail dot com
16 years ago
One feature of PHP's processing of POST and GET variables is that it automatically decodes indexed form variable names.

I've seem innumerable projects that jump through extra & un-needed processing hoops to decode variables when PHP does it all for you:

Example pseudo code:

Many web sites do this:

<form ....>
<input name="person_0_first_name" value="john" />
<input name="person_0_last_name" value="smith" />
...

<input name="person_1_first_name" value="jane" />
<input name="person_1_last_name" value="jones" />
</form>

When they could do this:

<form ....>
<input name="person[0][first_name]" value="john" />
<input name="person[0][last_name]" value="smith" />
...
<input name="person[1][first_name]" value="jane" />
<input name="person[1][last_name]" value="jones" />
</form>

With the first example you'd have to do string parsing / regexes to get the correct values out so they can be married with other data in your app... whereas with the second example.. you will end up with something like:
<?php
var_dump
($_POST['person']);
//will get you something like:
array (
0 => array('first_name'=>'john','last_name'=>'smith'),
1 => array('first_name'=>'jane','last_name'=>'jones'),
)
?>

This is invaluable when you want to link various posted form data to other hashes on the server side, when you need to store posted data in separate "compartment" arrays or when you want to link your POSTed data into different record handlers in various Frameworks.

Remember also that using [] as in index will cause a sequential numeric array to be created once the data is posted, so sometimes it's better to define your indexes explicitly.
up
77
darren_wheatley at hotmail dot com
9 years ago
I know it's a pretty basic thing but I had issues trying to access the $_POST variable on a form submission from my HTML page. It took me ages to work out and I couldn't find the help I needed in google. Hence this post.

Make sure your input items have the NAME attribute. The id attribute is not enough! The name attribute on your input controls is what $_POST uses to index the data and therefore show the results.
up
40
php (at) vxvr /dot de
3 years ago
If you want to receive application/json post data in your script you can not use $_POST. $_POST does only handle form data.
Read from php://input instead. You can use fopen or file_get_contents.

Example:

<?php
// Get the JSON contents
$json = file_get_contents('php://input');

// decode the json data
$data = json_decode($json);
?>
up
27
woodhavenbp at yahoo dot com
8 years ago
There's an earlier note here about correctly referencing elements in $_POST which is accurate.  $_POST is an associative array indexed by form element NAMES, not IDs.  One way to think of it is like this:  element "id=" is for CSS, while element "name=" is for PHP.  If you are referring to your element ID in the POST array, it won't work.  You must assign a name attribute to your element to reference it correctly in the POST array.  These two attributes can be the same for simplicity, i.e.,
<input type="text" id="txtForm" name="txtForm">...</input>
up
34
CXJ
10 years ago
Note that $_POST is NOT set for all HTTP POST operations,  but only for specific types of POST operations.  I have not been able to find documentation, but here's what I've found so far.

$_POST _is_ set for:

Content-Type: application/x-www-form-urlencoded

In other words,  for standard web forms.

$_POST is NOT set for:

Content-Type:text/xml

A type used for a generic HTTP POST operation.
up
15
paul at youngish dot homelinux^org
16 years ago
For a page with multiple forms here is one way of processing the different POST values that you may receive.  This code is good for when you have distinct forms on a page.  Adding another form only requires an extra entry in the array and switch statements.

<?php

if (!empty($_POST))
{
   
// Array of post values for each different form on your page.
   
$postNameArr = array('F1_Submit', 'F2_Submit', 'F3_Submit');       

   
// Find all of the post identifiers within $_POST
   
$postIdentifierArr = array();
       
    foreach (
$postNameArr as $postName)
    {
        if (
array_key_exists($postName, $_POST))
        {
            
$postIdentifierArr[] = $postName;
        }
    }

   
// Only one form should be submitted at a time so we should have one
    // post identifier.  The die statements here are pretty harsh you may consider
    // a warning rather than this.
   
if (count($postIdentifierArr) != 1)
    {
       
count($postIdentifierArr) < 1 or
            die(
"\$_POST contained more than one post identifier: " .
              
implode(" ", $postIdentifierArr));

       
// We have not died yet so we must have less than one.
       
die("\$_POST did not contain a known post identifier.");
    }
        
    switch (
$postIdentifierArr[0])
    {
    case
'F1_Submit':
       echo
"Perform actual code for F1_Submit.";
       break;

    case
'Modify':
       echo
"Perform actual code for F2_Submit.";
       break;
          
    case
'Delete':
       echo
"Perform actual code for F3_Submit.";
       break;
    }
}
else
// $_POST is empty.
{
    echo
"Perform code for page without POST data. ";
}
?>
To Top