Updated the variables_order description. This closes bug #36739

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@228378 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Philip Olson 2007-01-29 03:53:04 +00:00
parent b75f1750f7
commit 3f049c9792

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.44 $ -->
<?ml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.45 $ -->
<appendix id="ini">
<title>&php.ini; directives</title>
@ -3098,16 +3098,39 @@
</term>
<listitem>
<para>
Set the order of the EGPCS (Environment, GET, POST, Cookie,
Server) variable parsing. The default setting of this
directive is "EGPCS". Setting this to "GP", for example,
will cause PHP to completely ignore environment variables,
cookies and server variables, and to overwrite any GET
method variables with POST-method variables of the same name.
Sets the order of the EGPCS (<literal>E</literal>nvironment,
<literal>G</literal>et, <literal>P</literal>ost,
<literal>C</literal>ookie, and <literal>S</literal>erver) variable
parsing. For example, if variables_order
is set to <literal>"SP"</literal> then PHP will create the
&link.superglobals; <varname>$_SERVER</varname> and
<varname>$_POST</varname>, but not create
<varname>$_ENV</varname>, <varname>$_GET</varname>, and
<varname>$_COOKIE</varname>. Setting to "" means no
&link.superglobals; will be set.
</para>
<para>
See also <link linkend="ini.register-globals">register_globals</link>.
If the deprecated
<link linkend="ini.register-globals">register_globals</link>
directive is on (removed as of PHP 6), then variables_order also
configures the order the <literal>ENV</literal>,
<literal>GET</literal>, <literal>POST</literal>,
<literal>COOKIE</literal> and <literal>SERVER</literal> variables
are populated in global scope. So for example if variables_order
is set to <literal>"EGPCS"</literal>, register_globals is enabled,
and both <varname>$_GET['action']</varname> and
<varname>$_POST['action']</varname> are set, then
<varname>$action</varname> will contain the value of
<varname>$_POST['action']</varname> as <literal>P</literal> comes
after <literal>G</literal> in our example directive value.
</para>
<note>
<para>
The content and order of
<link linkend="reserved.variables.request">$_REQUEST</link> is also
affected by this directive.
</para>
</note>
</listitem>
</varlistentry>