On Thu, Dec 13, 2001 at 03:04:28PM -0500, Glenn Maynard wrote: > 02:46pm [EMAIL PROTECTED]/6 [~/lftp/src] ./lftp 0 > lftp 0:~> cd cs > ---- Connecting to 0 (0.0.0.0) port 21 > cd ok, cwd=/cs > lftp 0:/cs> cls -ld > drwxr-xr-x 4 glenn users 68 Dec 9 04:14 ./ > for comparison: > 03:02pm [EMAIL PROTECTED]/2 [~ftp/cs] ls -ld > drwxr-xr-x 4 glenn users 68 Dec 8 23:14 ./ > > which was really nice. Is this for the http HEAD problem? I havn't > looked at that; perhaps making directory-type caching work for that > would help? (not sure, the concept of a "directory" is gone with http > ...)
Er, I think just implementing ParseLongList for http should solve that problem. (Were there other reasons for this?) Comment on directories and HTTP before I noticed this: 03:55pm [EMAIL PROTECTED]/6 [~/lftp/src] ./lftp http://www.google.com cd ok, cwd=/ lftp www.google.com:/> cls 3.html about.html ads/ advanced_search images/ language_tools news/ preferences services/ lftp www.google.com:/> cd advanced_search cd: Access failed: 404 Not Found (/advanced_search) lftp www.google.com:/> cd services/ cd ok, cwd=/services lftp www.google.com:/services> cls chart1.gif chart2.gif custom.html customsitesearch.html free.html silver_gold.html site_compare.html web_compare.html I don't think there's any reason I shouldn't be able to cd to any of these, since they're all just links. This is a bit murky. For purposes of Chdir(), tab completion, GetFileInfo (when showdirs is false), etc., everything should be a directory in http. -- Glenn Maynard
