CoreFTP not handling permissions properly -550 at wrong time
Posted: Wed Oct 15, 2008 12:01 pm
I note with interest that windows FTP client isnt able to use CoreFTP properly because CoreFTP first says OK, then dsays DENY to a folder where there is no list permission.
As such we see this in FileZilla:
Command: CWD /tst
Response: 250 CWD command successful
Command: PORT 10,0,0,51,12,16
Response: 200 PORT command successful
Command: LIST
Response: 150 Opening ASCII mode data connection
Response: 550 Access is denied...
Error: Failed to retrieve directory listing
Note that the server agrees to start the LIST, with a 150 response, then issues a 550 denied.
Why does it not say "550" to the LIST? there is no list permission!
Windows FTP hangs, because it has received a 150 OK, and then it just sits and waits for the server to connect, but it never will.
Press Ctrl+C in windows FTP, and THEN we see the 550 denied message
If core had send the 550 denied earlier (i.e. in response to the LIST, windows FTP would not have hung)
As such we see this in FileZilla:
Command: CWD /tst
Response: 250 CWD command successful
Command: PORT 10,0,0,51,12,16
Response: 200 PORT command successful
Command: LIST
Response: 150 Opening ASCII mode data connection
Response: 550 Access is denied...
Error: Failed to retrieve directory listing
Note that the server agrees to start the LIST, with a 150 response, then issues a 550 denied.
Why does it not say "550" to the LIST? there is no list permission!
Windows FTP hangs, because it has received a 150 OK, and then it just sits and waits for the server to connect, but it never will.
Press Ctrl+C in windows FTP, and THEN we see the 550 denied message
If core had send the 550 denied earlier (i.e. in response to the LIST, windows FTP would not have hung)