Two answers: (A) I do think an override is a good idea. There may be some cases where extension code may need to hook a wrapper whether allow_url_fopen is enabled or not. Granted the code could temporarily change that value, but that's a hackish approach.
(B) I don't think SOAP is one of those cases. I would be dissapointed if SOAP allowed *any* calls to be made when allow_url_fopen is off. "Wez Furlong" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] A bit of a WTF factor. The reason is doesn't work is because php_stream_locate_url_wrapper() respects allow_url_fopen(), and the soap code interprets failure as "SSL not enabled in this build" which is wrong. It it passed in the REPORT_ERRORS flag, the correct reason would be emitted or logged somewhere. There is currently no flag that can override the allow_url_fopen check in php_stream_locate_url_wrapper. The question is: should we bypass this check for SOAP? If not, we need to tweak the docs and have the soap extension report a more appropriate reason for failure. --Wez. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
