Re: publicfile/ftpd and chrome

Glenn Willen wrote:
> Otavio,
> 
> That's very odd. Are you quite sure you asked chrome for
> "ftp://site/oexel/nc.exe", and not "ftp://site/nc.exe"?

Glenn,

please accept my apologies!
you're right, I had asked for "site/nc.exe"
here is the correct output:

26062 < USER anonymous 
26062 > 230 Hi. No need to log in; I'm an anonymous ftp server. 
26062 < SYST 
26062 > 215 UNIX Type: L8 
26062 < PWD 
26062 > 257 "/"  
26062 < TYPE I 
26062 > 200 Okay, using binary. 
26062 < EPSV 
26062 > 502 Sorry, I don't understand that command. 
26062 < PASV 
26062 > 227 Entering Passive Mode (201,90,227,216,176,163) 
26062 < SIZE /oexel/nc.exe 
192.168.1.233 dir ./oexel/nc.exe: success
26062 > 213 59392 
26062 < CWD /oexel/nc.exe 
26062 > 250 "/oexel/nc.exe"  
26062 < LIST 
192.168.1.233 dir ./oexel/nc.exe/: open failed: not a directory
26062 > 550 Sorry, I can't open that file: not a directory. 
26062 < QUIT 
26062 > 221 Bye. 
26062 > [EOF]

now I can see that the problem is that ftpd answered
"CWD /oexel/nc.exe" with OK.

is that odd behavior of ftpd concerning CWD needed?
I vaguely remember I argued with djb over this behavior
when publicfile was released...

[]s,

-- 
Otavio Exel /<\oo/>\ [email protected]