Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13548 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 99595 invoked by uid 1010); 27 Oct 2004 00:00:04 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 99559 invoked from network); 27 Oct 2004 00:00:03 -0000 Received: from unknown (HELO newweb.akbkhome.com) (202.81.246.113) by pb1.pair.com with SMTP; 27 Oct 2004 00:00:03 -0000 Received: from develop ([192.168.0.40] ident=alan) by newweb.akbkhome.com with esmtp (Exim 4.33) id 1CMbU4-0000eI-L0; Wed, 27 Oct 2004 08:16:13 +0800 Message-ID: <417EE61A.2080708@akbkhome.com> Date: Wed, 27 Oct 2004 08:04:42 +0800 User-Agent: Mozilla Thunderbird 0.8 (X11/20040926) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rob Richards CC: Wez Furlong , internals@lists.php.net References: <064a01c4bb82$8f9d4d90$f7dea8c0@cyberware.local> <417E929B.2040301@cschneid.com> <078e01c4bb96$86a0f340$f7dea8c0@cyberware.local> <4e89b4260410261323dc4d6da@mail.gmail.com> <087801c4bba4$53904150$f7dea8c0@cyberware.local> In-Reply-To: <087801c4bba4$53904150$f7dea8c0@cyberware.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: streams file uri under windows From: alan@akbkhome.com (Alan Knowles) you could follow the nautilus standard for this and use smb://hostname/sharename/file.txt ? Regards Alan Rob Richards wrote: >I ended up on this tangent only because file:/// support is needed (and from >the looks of things is the prefered method for local files over using >file://) and how I got stuck in the remote host issue. > >The following are some syntaxes which are used in windows (tested these with >a few browsers and html editors): >file://///remotehost/sharename/file.txt >file:///D|/file.txt - D being the drive letter >file:///D:/file.txt >file://D:/file.txt >file://D|/file.txt > >note that file:///\\remotehost\share\file.txt did work under IE and firefox > >Now, the only reason I am bringing this up as if I were to add the proposed >change, anything (as long as prefixed with file:///) would pass that remote >host check on windows - how it was before. What is currently there (the >change from 8/31) looks way to strict imho as it only allows the format >file://D: and nothing else. So it boils down to if there needs to be remote >host checking there what is the best way to do it given some of the URIs I >mentioned above (otherwise it might as well not be tested under windows >since my change to allow file:/// would allow all paths and invalid paths >would get caught when the stream was actually tried to be accessed). > >Rob > > >From: Wez Furlong > > > > >>The problem with file:// is that the spec deliberately does not define >>exactly how file://remotehost/.... works. >> >>Should file://\\\\remotehost\\share should work ? I guess it is >>roughly equivalent to file:///fully/qualified/path, in which case it >>should work. >> >>--Wez. >> >> > > >