- From: Graham Klyne <gk@ninebynine.org>
- Date: Fri, 13 May 2005 15:13:53 +0100
- To: John Cowan <jcowan@reutershealth.com>
- Cc: uri@w3.org
At 08:51 13/05/05 -0400, John Cowan wrote: > > (I would argue that converting file:/// to ftp:/// in the absence of > > specific knowledge about the host system is broken.) > >I am not aware of any browser that actually does that; certainly >Lynx (or more accurately libwww) does not, as a quick test will >make clear. What it does do is convert "file://example.com/..." >into "ftp://example.com/...", which is entirely plausible. I would argue that this, too, is broken as a general conversion: an FTP server at a given host is capable of serving just a subtree of the file system; e.g., FTP servers may 'chroot' to a restricted directory for anonymous access. #g ------------ Graham Klyne For email: http://www.ninebynine.org/#Contact
Received on Friday, 13 May 2005 20:13:50 UTC