Arne Caspari <[EMAIL PROTECTED]> writes:
> When called like:
> wget user:[EMAIL PROTECTED]/foo/bar/file.tgz
>
> and foo or bar is a read/execute protected directory while file.tgz is
> user-readable, wget fails to retrieve the file because it tries to CWD
> into the directory first.
>
> I think the correct behaviour should be not to CWD into the
> directory but to issue a GET request with the full path instead (
> which will succeed ).
I believe that CWD is mandated by the FTP specification, but you're
also right that Wget should try both variants. You can force Wget
into getting the file without CWD using this kludge:
wget ftp://user:[EMAIL PROTECTED]/%2Ffoo%2Fbar%2Ffile.tgz -O file.tgz
