Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17433 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88420 invoked by uid 1010); 27 Jul 2005 22:50:09 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 88405 invoked from network); 27 Jul 2005 22:50:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jul 2005 22:50:09 -0000 X-Host-Fingerprint: 70.85.46.36 unknown Received: from ([70.85.46.36:50191] helo=prohost.org) by pb1.pair.com (ecelerity 2.0 beta r(6227M)) with SMTP id 50/F7-58254-1AF08E24 for ; Wed, 27 Jul 2005 18:50:09 -0400 Received: (qmail 25416 invoked from network); 27 Jul 2005 22:50:06 -0000 Received: from cpe00095beeab35-cm000f9f7d6664.cpe.net.cable.rogers.com (HELO ?192.168.1.101?) (69.196.31.219) by prohost.org with SMTP; 27 Jul 2005 22:50:06 -0000 Message-ID: <42E80F9D.40005@prohost.org> Date: Wed, 27 Jul 2005 18:50:05 -0400 User-Agent: Mozilla Thunderbird 1.0 - [MOOX M3] (Windows/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adam Maccabee Trachtenberg CC: Sara Golemon , internals@lists.php.net References: <4e89b42605072713575d8f0d57@mail.gmail.com> <04.A5.58254.87408E24@pb1.pair.com> In-Reply-To: X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: SOAP SSL support doesn't work when allow_url_fopen is turned off From: ilia@prohost.org (Ilia Alshanetsky) Adam Maccabee Trachtenberg wrote: > I pretty much take it for granted that people are going to need to > fetch the WSDL file from a remote location. Not to mention do anything useful with it, like run queries :-) > Are you therefore saying SOAP support should be 100% diabled when > allow_url_fopen is off? SOAP is not disabled, simply prevented from querying remote data sources directly. > Do you apply the same limitations to, for > example, cURL? No, nor does it prevent fsockopen() or equivalent from being used to run queries. Ilia