When using PHP with track_vars On and register_globals Off (recommended
setting), PHP doesn't know the built-in system and environment vars
anymore.

For example, $PHP_SELF becomes and unknow variable.

This is really annoying.

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 correct way would be to use $_SERVER['PHP_SELF'] ; this is
guaranteed to work with and without register_globals = off.

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.. 

Valid point. I'm reopening this as a documentation problem.

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!

It's printed in _SERVER too (apache 1.3.22/php 4.1.0).

Tested again. Yes you are right. It would be good
to have it listed only in _SERVER, as the other vars.

but $PHP_SELF is also a special variable, so I think also listing it out
of any collection is a good thing.

This has been fixed in CVS.

FWIW, I think that if $PHP_SELF is to be documented outside
of the $_SERVER list, it should be worded carefully
to prevent users wondering why $PHP_SELF isn't available in 
the global scope.

Torben

This has been fixed in CVS.

FWIW, I think that if $PHP_SELF is to be documented outside
of the $_SERVER list, it should be worded carefully
to prevent users wondering why $PHP_SELF isn't available in 
the global scope.

Torben