Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17430 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32204 invoked by uid 1010); 27 Jul 2005 20:57:18 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 32188 invoked from network); 27 Jul 2005 20:57:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jul 2005 20:57:18 -0000 X-Host-Fingerprint: 64.233.184.195 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.195:18655] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6227M)) with SMTP id 64/11-58254-D25F7E24 for ; Wed, 27 Jul 2005 16:57:17 -0400 Received: by wproxy.gmail.com with SMTP id i21so255418wra for ; Wed, 27 Jul 2005 13:57:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=BN+hO86e22N2iaqyX3sF23KsFG4vd4UmqvmAXBVWGylaNwWTaFrw7vRinXmVgLwONoxUByz6fFV5GoYV6gNhEu/ro2pnoh46dcT4KwgdC6QoJCqbVYAlcky7fVLz0N/kkG3aBjdlJCjG1LDc8hGLbTUD1IeZjBUSnkA6BLyY9PM= Received: by 10.54.31.37 with SMTP id e37mr489444wre; Wed, 27 Jul 2005 13:57:15 -0700 (PDT) Received: by 10.54.153.5 with HTTP; Wed, 27 Jul 2005 13:57:14 -0700 (PDT) Message-ID: <4e89b42605072713575d8f0d57@mail.gmail.com> Date: Wed, 27 Jul 2005 16:57:14 -0400 Reply-To: Wez Furlong To: PHPdev , Dmitry Stogov Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: SOAP SSL support doesn't work when allow_url_fopen is turned off From: kingwez@gmail.com (Wez Furlong) 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.