Re: potential solution to user streams + allow_url_include=off

Stanislav Malyshev wrote: > oh, and I forgot another thing: > > 5. Have some function like stream_is_remote() which could check URL for > remote-ness, > so that the responsible stream wrapped would not rely on fopen erroring > out. > I couldn't locate such function, so if it isn't there it should be added. > >> I think the problem could be solved this way: >> 0. allow_url_include and allow_url_fopen renamed to >> allow_remote_include and allow_remote_fopen (not really necessary, >> just much cleaner, if you don't like it, ignore it for now). >> 1. By default, allow_remote_inclue=0, allow_remote_fopen=1 >> 2. Stream can be of three types - remote, local and user/local. >> 3. User streams can be declared when registered as either remote or >> user/local, remote being the default. >> 4. When operation on user/local stream is run, allow_remote_fopen is >> disabled if allow_remote_include was disabled. This is cleaner than my suggestion, I like it. It would also be very easy to implement. Greg