Re: allow_url_fopen / allow_url_include and fine grained control

From: Date: Thu, 18 Jan 2007 20:38:35 +0000
Subject: Re: allow_url_fopen / allow_url_include and fine grained control
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-27526@lists.php.net to get a copy of this message
I assume this would also mean all userland stream wrappers become is_url=1? Anyway, +1. This patch, by itself, doesn't affect the is_urlness of userspace wrappers. Whether or not we change their designation is up to a separate concensus (I'm in favor of it for the record).
Funnily enough though, Pierre and I were just discussing the problem of userspace wrappers. Specifying all potential userspace wrapper names in a whitelist style allow_url_fopen setting isn't realistic, so we thought it might be a good idea to add a sort of "meta-wrapper" name to be used in the whitelist style. e.g. allow_url_fopen=file,http,ftp,user would allow those first three wrappers explicitly by name, plus any userdefined wrapper (regardless of specific name). For completeness, we might also add a metawrapper called "internal" for "All non-userspace based wrappers", though the specific usefulness of that is a little more iffy... -Sara

« previous php.internals (#27526) next »