Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17431 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68847 invoked by uid 1010); 27 Jul 2005 22:02:33 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 68832 invoked from network); 27 Jul 2005 22:02:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jul 2005 22:02:33 -0000 X-Host-Fingerprint: 69.12.155.129 talos.alphaweb.net Received: from ([69.12.155.129:26978] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6227M)) with SMTP id 04/A5-58254-87408E24 for ; Wed, 27 Jul 2005 18:02:32 -0400 Message-ID: <04.A5.58254.87408E24@pb1.pair.com> To: internals@lists.php.net References: <4e89b42605072713575d8f0d57@mail.gmail.com> Date: Wed, 27 Jul 2005 14:31:54 -0700 Lines: 29 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-RFC2646: Format=Flowed; Original X-Posted-By: 69.12.155.129 Subject: Re: SOAP SSL support doesn't work when allow_url_fopen is turned off From: pollita@php.net ("Sara Golemon") 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" wrote in message news:4e89b42605072713575d8f0d57@mail.gmail.com... 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.