Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEAT command stops connection #3248

Closed
cyberduck opened this issue Jun 15, 2009 · 4 comments
Closed

FEAT command stops connection #3248

cyberduck opened this issue Jun 15, 2009 · 4 comments
Assignees
Labels
bug ftp FTP Protocol Implementation thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

25cab1e created the issue

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?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

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.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

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

@cyberduck
Copy link
Collaborator Author

stillerleser commented

Replying to [comment:1 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"?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 stillerleser]:

Replying to [comment:1 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?

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug ftp FTP Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

2 participants