Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17571 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13413 invoked by uid 1010); 7 Aug 2005 14:00:52 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 13397 invoked from network); 7 Aug 2005 14:00:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Aug 2005 14:00:52 -0000 X-Host-Fingerprint: 216.117.147.250 unknown Linux 2.4/2.6 Received: from ([216.117.147.250:45358] helo=ctindustries.net) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 1F/C8-04646-31416F24 for ; Sun, 07 Aug 2005 10:00:51 -0400 Received: from [127.0.0.1] (dsta-aa203.pivot.net [66.186.171.203]) (authenticated bits=0) by ctindustries.net (8.12.8/8.12.8) with ESMTP id j77CpWtI032271 for ; Sun, 7 Aug 2005 08:51:35 -0400 Message-ID: <42F61570.5080803@ctindustries.net> Date: Sun, 07 Aug 2005 10:06:40 -0400 User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "internals@lists.php.net" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.86.2/1006/Sat Aug 6 16:02:09 2005 on ctindustries.net X-Virus-Status: Clean Subject: XML URIs and streams From: rrichards@ctindustries.net (Rob Richards) Just realized there is an issue with URI handling and XML. Problem deals with escaping and non-filesystem URIs. Doesn't work unless URI gets double escaped. Have a patch that's only been tested a bit with latest libxml so far, though I dont forsee any issues with earlier versions. http://www.ctindustries.net/patches/libxml.diff.txt The issue is it may break existing apps that double escape only the arguments and not the entire URI. It will though make it work like the rest of the stream based functions like file_get_contents, but still allow the loading of a URI that has been completely escaped, which the other functions fail on but worked for xml under PHP 5.0. I'm out for the week as of tomorrow morning but would like to get some fix in for 5.1. Should I commit now to get it into RC1, wait till I get back and do more testing first, or not do it since it potentially will break some apps. Personally I think what it fixes greatly outweighs any potential breakage. Rob