Cyberduck Mountain Duck CLI

#3248 closed defect (thirdparty)

FEAT command stops connection

Reported by: stillerleser@… Owned by: dkocher
Priority: normal Milestone:
Component: ftp Version: 3.2
Severity: normal Keywords: ftp feat-command
Cc: Architecture:
Platform:

Description

I try to establish a connection, but I get always the same result: After login something ends the connection. Here is a snippet from the login log:

220 FTP Server ready.
USER blabla
331 Password required for 3137-975
PASS ****
230 User blabla logged in
FEAT
500 Invalid command: try being more creative
PWD
211-Features:
 MDTM
 MFMT
 MFF modify;UNIX.group;UNIX.mode;
 MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.mode*;UNIX.owner*;
 REST STREAM
 SIZE
211 End

and then the connection is ended. With FTP on cmd line I don't have any problems to login.

Is there a chance to configure the login procedure? Maybe to establish a connection without any automatic commands from cyberduck?

Change History (4)

comment:1 follow-up: Changed on Jun 15, 2009 at 8:22:43 PM by dkocher

  • Resolution set to thirdparty
  • Status changed from new to closed

There is currently no workaround to disable sending the FEAT command. But the transcript clearly shows the server is responds with a 500 error message (which is not an issue), but then later fails to respond correctly to PWD but sends the listing for the previous request instead.

comment:2 Changed on Jun 15, 2009 at 9:03:36 PM by dkocher

Actually there was just #3247 reported also which looks like a duplicate. Will have to look into this further.

comment:3 in reply to: ↑ 1 ; follow-up: Changed on Sep 25, 2009 at 4:41:52 PM by stillerleser

Replying to dkocher:

the server is responds with a 500 error message

I checked this with ftp on shell. FEAT returns an error, FEATU does not. Maybe I have there an weird FTP server, but would this against an RFC if you implement "FEATU" inspite of "FEAT"?

comment:4 in reply to: ↑ 3 Changed on Sep 25, 2009 at 6:35:34 PM by dkocher

Replying to stillerleser:

Replying to dkocher:

the server is responds with a 500 error message

I checked this with ftp on shell. FEAT returns an error, FEATU does not. Maybe I have there an weird FTP server, but would this against an RFC if you implement "FEATU" inspite of "FEAT"?

Can you point me to an RFC describing FEATU?

Note: See TracTickets for help on using tickets.
swiss made software