-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Daniel Stenberg wrote: > On Fri, 3 Aug 2007, Micah Cowan wrote: > >> I have a question: why do we attempt to generate absolute paths and >> such and CWD to those, instead of just doing the portable >> string-of-CWDs to get where we need to be? > > Just a word of caution here: while RFC1738 tells this is the way to do > it, there are servers and times where this approach doesn't work. > (lib)curl has an option to specify the CWD style (multiple cwd, single > cwd or no cwd) due to this...
Could you be more specific about how it fails to work on some systems? I understand (from comments in wget) that OS/400 doesn't support hierarchies: but then no legitimate OS/400 FTP URL would include more than one dir component in its path. Given that probably most other user-agents follow the RFC in this regard, I'm having a little problem seeing how an FTP server that can't handle this could survive, particularly since, from the beginning of time, it's been the only way to reliably specify the directory path one wants. >> Technically, we can violate the RFCs (specifically, RFC 1738, which >> defines the ftp URL scheme in terms of a string of CWDs from the >> starting directory), if the FTP server starts us out in a directory >> other than / > > The particular login directory doesn't affect the CWD approach at all, > since the URL gives the path relative to the login directory... Do you mean that wget tacks the path onto the value it gets from PWD, then? - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGtMn07M8hyUobTrERCPgQAJ9oFSrUYB88x+rvco/EbPEsgUr0/QCdF6WE Ih2fbwL4YAuSZAimHKrIGOI= =/fE7 -----END PGP SIGNATURE-----
