Stanislav Malyshev wrote: > Hi! > >>> This would break security distinction between file ops and include ops, >>> when URLs are allowed for open but not include. > > Additional thing - it probably would be a problem for bytecode caches, > since they'd have to: > a. watch all file opens, in case some of these will later be used for > include > b. somehow be able to get filename back from open stream to get the > cached file. Hi again,
A good point. Fortunately, most streams do store the filename in the stream struct, so this would still probably be possible in the majority of cases. If not available, the original requested filename is used (the one from the fopen call), so opcode caches probably could just use that. Greg -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
