Bug #14734 Updated: new superglobals ($_SERVER, etc.) not documented

ID: 14734 Updated by: mfischer Reported By: abraham_guyt@bigfoot.com Status: Open Bug Type: Documentation problem Operating System: Win XP PHP Version: 4.1.0 New Comment: It's printed in _SERVER too (apache 1.3.22/php 4.1.0). Previous Comments: ------------------------------------------------------------------------ [2001-12-28 10:17:17] goba@php.net Just a note: in the PHP 4.1.0 phpinfo() output, all the predefined vars are printed as _SERVER and _ENV members, except PHP_SELF, it is printed alone, and not in any array. This must be corrected! ------------------------------------------------------------------------ [2001-12-28 10:05:28] mfischer@php.net Valid point. I'm reopening this as a documentation problem. ------------------------------------------------------------------------ [2001-12-28 10:01:35] abraham_guyt@bigfoot.com Hi All, Thanks for the replies. The docs tell me that using globally registered vars presents a security risk and is being turned off in future versions anyway, so it's quite necessary to get accustomed to it. Using $_SERVER['PHP_SELF'] must be the way to go. However, where to find proper documentation on these 'new' vars ? I can't find them, only some pages mentioning they exist.. ------------------------------------------------------------------------ [2001-12-28 09:56:13] mfischer@php.net The correct way would be to use $_SERVER['PHP_SELF'] ; this is guaranteed to work with and without register_globals = off. ------------------------------------------------------------------------ [2001-12-28 09:34:57] rasmus@php.net Then don't turn register_globals off. Turning off register_globals gets rid of all the globals. If you still want some, leave it turned on, but simply set your variables_order directive in your php.ini file to reflect which globals you want. For example, if you want environment and server variables, set it to "ES" ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/?id=14734 Edit this bug report at http://bugs.php.net/?id=14734&edit=1