Re: wget BUG: ftp file retrieval

[Arne Caspari]

Thank you all for your very fast response. As a further note: When this 
error occurs, wget bails out with the following error message:

"No such directory foo/bar".

I think it should instead be "Could not access foo/bar: Permission 
denied" or similar in such a situation.


/Arne


Mauro Tortonesi wrote:


Hrvoje Niksic wrote:


Arne Caspari <[EMAIL PROTECTED]> writes:

I believe that CWD is mandated by the FTP specification, but you're
also right that Wget should try both variants.



i agree. perhaps when retrieving file A/B/F.X we should try to use:

GET A/B/F.X

first, then:

CWD A/B
GET F.X

if the previous attempt failed, and:

CWD A
CDW B
GET F.X

as a last resort. what do you think?

wget BUG: ftp file retrieval

[Arne Caspari]

Hello,

current wget seems to have the following bug in the ftp retrieval code:

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 ).


Best regards,

Arne Caspari