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

Subsequent commands fail after FEAT with error response #4200

Closed
cyberduck opened this issue Feb 5, 2010 · 6 comments
Closed

Subsequent commands fail after FEAT with error response #4200

cyberduck opened this issue Feb 5, 2010 · 6 comments
Assignees
Labels
bug ftp FTP Protocol Implementation thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

4c236da created the issue

Some of my bookmarks are not working:

  1. dblclick bookmark
  2. status shows I am logging in, ends with 'login successful'
  3. after this I remain at the bookmarks list, and status shows '25 bookmarks'.

Expected behaviour:
3. I get shown a listing.

The log pane shows this:

USER username
331 User username OK. Password required
PASS ********
230-User username has group access to:  client0 
230 OK. Current restricted directory is /
FEAT
500 ?
PWD
211-Extensions supported:
 EPRT
 IDLE
 MDTM
 SIZE
 REST STREAM
 MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
 MLSD
 TVFS
 ESTP
 PASV
 EPSV
 SPSV
 ESTA
 AUTH TLS
 PBSZ
 PROT
 UTF8
211 End.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This looks like a server issue to me. First it gives an 500 unknown command response to FEAT which is followed by a PWD request from Cyberduck. But the response for the working directory is not a path but the supported features response expected for the first command. Do you succeed connecting using another client? If so, please post the other transcript.

@cyberduck
Copy link
Collaborator Author

4c236da commented

Yes, with Filezilla I connect fine.

Here is the transcript from Filezilla:

Status:	Resolving address of [HOST URL]
Status:	Connecting to [IP:PORT]...
Status:	Connection established, waiting for welcome message...
Response:	220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Response:	220-You are user number 1 of 50 allowed.
Response:	220-Local time is now 00:52. Server port: 21.
Response:	220-This is a private system - No anonymous login
Response:	220-IPv6 connections are also welcome on this server.
Response:	220 You will be disconnected after 15 minutes of inactivity.
Command:	USER [USERNAME]
Response:	331 User [USERNAME] OK. Password required
Command:	PASS *************
Response:	230-User [USERNAME] has group access to:  client0 
Response:	230 OK. Current restricted directory is /
Command:	SYST
Response:	215 UNIX Type: L8
Command:	FEAT
Response:	211-Extensions supported:
Response:	 EPRT
Response:	 IDLE
Response:	 MDTM
Response:	 SIZE
Response:	 REST STREAM
Response:	 MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
Response:	 MLSD
Response:	 TVFS
Response:	 ESTP
Response:	 PASV
Response:	 EPSV
Response:	 SPSV
Response:	 ESTA
Response:	 AUTH TLS
Response:	 PBSZ
Response:	 PROT
Response:	 UTF8
Response:	211 End.
Command:	OPTS UTF8 ON
Response:	200 OK, UTF-8 enabled
Status:	Connected
Status:	Retrieving directory listing...
Command:	PWD
Response:	257 "/" is your current location
Command:	TYPE I
Response:	200 TYPE is now 8-bit binary
Command:	PASV
Response:	227 Entering Passive Mode (174,142,29,77,213,126)
Command:	MLSD
Response:	150 Accepted data connection
Response:	226-ASCII
Response:	226-Options: -l 
Response:	226 3 matches total
Status:	Directory listing successful

@cyberduck
Copy link
Collaborator Author

4c236da commented

Please could this be reopened? I don't have the permisisons to do so.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Still looks like a server issue. Don't know why it gives us a differnet response to FEAT than what Filezilla gets.

@cyberduck
Copy link
Collaborator Author

4c236da commented

This may well be a problem with the server being badly configured -- but other FTP clients I have tried with the same server Just Work -- just tried Flow and connected perfectly.

Therefore I think the problem lies with Cyberduck for falling over where other clients cope.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Is it possible to get access to the server for debugging the issue?

@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