Dennis Gearon wrote:
Why unset the globals?
I plan on implementing filters on all User input to ALL scripts in the
prepend file. And if someone wants to get a variable that was supplied
by a user, they have to specifiy if it's going to be INT, STR(with
options to remove run on spaces, validate em
Ok
Why not just set the values in $_REQUEST then?
AbstractEnvironment::stripTagsArr($_REQUEST);
Or something like this:
foreach($_REQUEST as $key => $val) {
$_REQUEST[$key] = stripTagsNStuff($key, $val);
}
On Thu, 15 Jul 2004 15:45:45 -0700, Dennis Gearon <[EMAIL PROTECTED]> wrote:
> I fo
I found the answer, as my second post on this told.
Why unset the globals?
I plan on implementing filters on all User input to ALL scripts in the prepend file.
And if someone wants to get a variable that was supplied by a user, they have to
specifiy if it's going to be INT, STR(with options to re
You can't unset $_REQUEST. All it does is unset the reference to it in
the current context. It still exists elsewhere. If you *really* want
to get rid of $_REQUEST, you should do it this way:
unset($GLOBALS['_REQUEST']);
But I would advise against that. Why exactly are you unsetting a superglobal
I have a function in a class that unsets the superglobal $_REQUEST;
Well, it's supposed to, it doesn't do it. I'm on version 4.2.3 of PHP. This page:
http://us2.php.net/manual/en/language.variables.predefined.php#language.variables.superglobals
says that $_REQUEST is a super global as of v
5 matches
Mail list logo
