Date: Tue, 5 Jul 2005 15:19:00 -0400 From: John Baldwin <jhb@FreeBSD.org> To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= <des@des.no> Cc: freebsd-net@FreeBSD.org Subject: Re: Bug in libfetch handling of FTP urls.. Message-ID: <200507051519.01251.jhb@FreeBSD.org> In-Reply-To: <86vf3rthf7.fsf@xps.des.no> References: <200506281338.14511.jhb@FreeBSD.org> <86vf3rthf7.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 03 July 2005 10:48 pm, Dag-Erling Sm=F8rgrav wrote: > John Baldwin <jhb@FreeBSD.org> writes: > > I verified this by doing 'fetch -vv' and seeing that it does one big CWD > > (instead of the multiple CWD's the RFC says should happen) and that it > > includes the leading '/' when it should not. > > I am currently testing a patch for this. Ok, thanks. > > Also, it seems that fetch ignores the ';type=3DX' optional part of the > > url-path and always uses TYPE I. > > Correct, that was never implemented. At the very least, the typecode > should be stripped from the URL. It does strip it out. ;type=3Dd support would be useful for some stuff I'm= =20 doing here at work but I've just punted for now and required an explicit=20 MANIFEST file that I fetch first and then parse. =2D-=20 John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200507051519.01251.jhb>