Date: Wed, 1 Oct 1997 11:54:28 -0700 From: John-Mark Gurney <gurney_j@efn.org> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: freebsd-bugs@hub.freebsd.org Subject: Re: bin/4670: /usr/bin/fetch fails to ftp a file ncftp can Message-ID: <19971001115428.03021@hydrogen.nike.efn.org> In-Reply-To: <199710011828.OAA19756@khavrinen.lcs.mit.edu>; from Garrett Wollman on Wed, Oct 01, 1997 at 02:28:46PM -0400 References: <199710011750.KAA27156@hub.freebsd.org> <199710011828.OAA19756@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Wollman scribbled this message on Oct 1: > <<On Wed, 1 Oct 1997 10:50:02 -0700 (PDT), John-Mark Gurney <gurney_j@efn.org> said: > > > now the question is, should we simply add a / to the front of the path > > in fetch? > > No. FTP URLs are SUPPOSED to be relative to wherever FTP puts > incoming users. If you want to add a literal `/' to the URL, add > `%2f' at the beginning. (Many URL parsers interpret this > incorrectly... the third slash in an absolute URL is ONLY a separator, > and does not comprise part of the `path' component.) yep... if you add a %2f, fetch will complete successfully.... so would adding a fourth slash to be relative be in spec? or are all repeate slashes suppose to be condensed? because fetch will work if you do: fetch ftp://ftp.fu-berlin.de//pub/... thanks for the clarification on the url's... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971001115428.03021>