From 64fb8f6a3873701196c842c35dc76e510593d0be Mon Sep 17 00:00:00 2001
From: Patrick Allaert <patrickallaert@php.net>
Date: Fri, 11 Aug 2017 18:49:46 +0000
Subject: [PATCH] Fixed: doc bug 74727

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@342844 c90b9560-bf6c-de11-be94-00142212c4b1
---
 language/variables.xml | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/language/variables.xml b/language/variables.xml
index 315189c5d4..16b1f3550c 100644
--- a/language/variables.xml
+++ b/language/variables.xml
@@ -1080,6 +1080,19 @@ $varname.ext;  /* invalid variable name */
      <function>is_string</function>.  See also the chapter on 
      <link linkend="language.types">Types</link>.
     </para>
+    <para>
+     HTTP being a text protocol, most, if not all, content that comes in
+     <link linkend="language.variables.globals">Superglobal arrays</link>, 
+     like <varname>$_POST</varname> and <varname>$_GET</varname> will remain
+     as strings. PHP will not try to convert values to a specific type.
+     In the example below, <varname>$_GET["var1"]</varname> will contain the
+     string "null" and <varname>$_GET["var2"]</varname>, the string "123".
+     <programlisting>
+<![CDATA[
+/index.php?var1=null&var2=123
+]]>
+      </programlisting>
+    </para>
    </sect2>
 
    <sect2 xml:id="language.variables.external.changelog">
@@ -1123,7 +1136,8 @@ $varname.ext;  /* invalid variable name */
         <row>
          <entry>4.1.0</entry>
          <entry>
-          <link linkend="language.variables.superglobals">Superglobal arrays</link>, 
+          <link linkend="language.variables.
+globals">Superglobal arrays</link>, 
           like <varname>$_POST</varname> and <varname>$_GET</varname> became 
           available
          </entry>