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

Jump to bottom

Could not parse response code #7445

Closed
cyberduck opened this issue Sep 12, 2013 · 6 comments
Closed

Could not parse response code #7445

cyberduck opened this issue Sep 12, 2013 · 6 comments
Assignees
@dkocher
Labels
bug fixed ftp FTP Protocol Implementation high priority
Milestone
4.4

Comments

@cyberduck
Copy link
Collaborator

202bcfe created the issue

Note that I am using: Version 4.4 (12675)

Woke up this morning after upgrading, never had this problem before. Started connecting to a client's server and then got this:

Listing directory failed

Could not parse response code.
Server Reply: 02-13-13  11:38AM       <DIR>          aspnet_client.

220 Microsoft FTP Service
SYST
530 Please login with USER and PASS.
FEAT
530 Please login with USER and PASS.
USER sr1776
331 Password required for sr1776.
PASS ********
230 User sr1776 logged in.
PWD
257 "/sr1776" is current directory.
STAT /sr1776
213-status of /sr1776:
05-10-13  11:45AM                 3703 activity.php
CWD /sr1776

Log view is below

220 Microsoft FTP Service
SYST
530 Please login with USER and PASS.
FEAT
530 Please login with USER and PASS.
USER sr1776
331 Password required for sr1776.
PASS ********
230 User sr1776 logged in.
PWD
257 "/sr1776" is current directory.
STAT /sr1776
213-status of /sr1776:
05-10-13  11:45AM                 3703 activity.php
CWD /sr1776
NOOP
220 Microsoft FTP Service
SYST
530 Please login with USER and PASS.
FEAT
530 Please login with USER and PASS.
USER sr1776
331 Password required for sr1776.
PASS ********
230 User sr1776 logged in.
QUIT
221
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [7445 sheldon kennedy]:

The interoperability failure is caused by the malformed response

213-status of /sr1776:

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Drop use of STAT in c66f612 on failure reading reply code.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Added tests in e192d09.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please update to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

202bcfe commented

Wow you are fast. Snapshot 12881 is the latest I see, so I'll wait a bit, perhaps it's still building on your end.

Donation coming your way.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:8 sheldon kennedy]:

Wow you are fast. Snapshot 12881 is the latest I see, so I'll wait a bit, perhaps it's still building on your end.

Donation coming your way.

Available in a few minutes. Please reopen this ticket if the issue persists with the latest build as I could not replicate the issue 1:1 against a live system. Would it be possible to get a test account on the server?

@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.
Assignees

@dkocher dkocher

Labels
bug fixed ftp FTP Protocol Implementation high priority
Projects
None yet
Milestone
4.4
Development

No branches or pull requests
2 participants
@dkocher @cyberduck